[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7310EDDPTA2F72VCGASFP0H":3,"skill-same:01M7310EDDPTA2F72VCGASFP0H":108},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M7310EDDPTA2F72VCGASFP0H","building-devsecops-pipeline-with-gitlab-ci",null,"Design and implement a comprehensive DevSecOps pipeline in GitLab CI\u002FCD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: building-devsecops-pipeline-with-gitlab-ci\ndescription: Design and implement a comprehensive DevSecOps pipeline in GitLab CI\u002FCD\n  integrating SAST, DAST, container scanning, dependency scanning, and secret detection.\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- gitlab-ci\n- devsecops\n- sast\n- dast\n- container-scanning\n- dependency-scanning\n- secret-detection\n- cicd-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- GV.SC-07\n- ID.IM-04\n- PR.PS-04\nmitre_attack:\n- T1195.001\n- T1195.002\n- T1552.001\n- T1190\n- T1610\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n\n# Building DevSecOps Pipeline with GitLab CI\n\n## Overview\n\nGitLab provides an integrated DevSecOps platform that embeds security testing directly into the CI\u002FCD pipeline. By leveraging GitLab's built-in security scanners---SAST, DAST, container scanning, dependency scanning, secret detection, and license compliance---teams can shift security left, catching vulnerabilities during development rather than post-deployment. GitLab Duo AI assists with false positive detection for SAST vulnerabilities, helping security teams focus on genuine issues.\n\n\n## When to Use\n\n- When deploying or configuring building devsecops pipeline with gitlab ci capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- GitLab Ultimate license (required for full security scanner suite)\n- GitLab Runner configured (shared or self-hosted)\n- `.gitlab-ci.yml` pipeline configuration familiarity\n- Docker-in-Docker (DinD) or Kaniko for container builds\n- Application deployed to a staging environment for DAST scanning\n\n## Core Security Scanning Stages\n\n### Static Application Security Testing (SAST)\n\nSAST analyzes source code for vulnerabilities before compilation. GitLab supports 14+ languages using analyzers such as Semgrep, SpotBugs, Gosec, Bandit, and NodeJsScan. The simplest inclusion uses GitLab's managed templates.\n\n### Dynamic Application Security Testing (DAST)\n\nDAST tests running applications by simulating attack payloads against HTTP endpoints. It detects XSS, SQLi, CSRF, and other runtime vulnerabilities that static analysis cannot find. DAST requires a deployed, accessible target URL.\n\n### Container Scanning\n\nUses Trivy to scan Docker images for known CVEs in OS packages and application dependencies. Runs after the Docker build stage to gate images before they reach a registry.\n\n### Dependency Scanning\n\nInspects dependency manifests (package.json, requirements.txt, pom.xml, Gemfile.lock) for known vulnerable versions. Operates at the source code level, complementing container scanning.\n\n### Secret Detection\n\nScans commits for accidentally committed credentials, API keys, tokens, and private keys using pattern matching and entropy analysis. Runs on every commit to prevent secrets from reaching the repository.\n\n## Implementation\n\n### Complete Pipeline Configuration\n\n```yaml\n# .gitlab-ci.yml\n\nstages:\n  - build\n  - test\n  - security\n  - deploy-staging\n  - dast\n  - deploy-production\n\nvariables:\n  DOCKER_IMAGE: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA\n  SECURE_LOG_LEVEL: \"info\"\n\n# Include GitLab managed security templates\ninclude:\n  - template: Security\u002FSAST.gitlab-ci.yml\n  - template: Security\u002FSecret-Detection.gitlab-ci.yml\n  - template: Security\u002FDependency-Scanning.gitlab-ci.yml\n  - template: Security\u002FContainer-Scanning.gitlab-ci.yml\n  - template: DAST.gitlab-ci.yml\n  - template: Security\u002FLicense-Scanning.gitlab-ci.yml\n\nbuild:\n  stage: build\n  image: docker:24.0\n  services:\n    - docker:24.0-dind\n  variables:\n    DOCKER_TLS_CERTDIR: \"\u002Fcerts\"\n  script:\n    - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY\n    - docker build -t $DOCKER_IMAGE .\n    - docker push $DOCKER_IMAGE\n  rules:\n    - if: $CI_COMMIT_BRANCH\n\nunit-tests:\n  stage: test\n  image: $DOCKER_IMAGE\n  script:\n    - npm ci\n    - npm run test:coverage\n  coverage: '\u002FLines\\s*:\\s*(\\d+\\.?\\d*)%\u002F'\n  artifacts:\n    reports:\n      junit: junit-report.xml\n      coverage_report:\n        coverage_format: cobertura\n        path: coverage\u002Fcobertura-coverage.xml\n\n# Override SAST to run in security stage\nsast:\n  stage: security\n  variables:\n    SAST_EXCLUDED_PATHS: \"spec,test,tests,tmp,node_modules\"\n    SEARCH_MAX_DEPTH: 10\n\n# Override container scanning\ncontainer_scanning:\n  stage: security\n  variables:\n    CS_IMAGE: $DOCKER_IMAGE\n    CS_SEVERITY_THRESHOLD: \"HIGH\"\n\n# Override dependency scanning\ndependency_scanning:\n  stage: security\n\n# Override secret detection\nsecret_detection:\n  stage: security\n\n# License compliance scanning\nlicense_scanning:\n  stage: security\n\ndeploy-staging:\n  stage: deploy-staging\n  image: bitnami\u002Fkubectl:latest\n  script:\n    - kubectl set image deployment\u002Fapp app=$DOCKER_IMAGE -n staging\n    - kubectl rollout status deployment\u002Fapp -n staging --timeout=300s\n  environment:\n    name: staging\n    url: https:\u002F\u002Fstaging.example.com\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\n# DAST runs against deployed staging\ndast:\n  stage: dast\n  variables:\n    DAST_WEBSITE: https:\u002F\u002Fstaging.example.com\n    DAST_FULL_SCAN_ENABLED: \"true\"\n    DAST_BROWSER_SCAN: \"true\"\n  needs:\n    - deploy-staging\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\ndeploy-production:\n  stage: deploy-production\n  image: bitnami\u002Fkubectl:latest\n  script:\n    - kubectl set image deployment\u002Fapp app=$DOCKER_IMAGE -n production\n    - kubectl rollout status deployment\u002Fapp -n production --timeout=300s\n  environment:\n    name: production\n    url: https:\u002F\u002Fapp.example.com\n  when: manual\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n```\n\n### Security Approval Policies\n\nConfigure scan execution policies to enforce mandatory security scans:\n\n1. Navigate to Security & Compliance > Policies\n2. Create a \"Scan Execution Policy\" requiring SAST and secret detection on all branches\n3. Create a \"Merge Request Approval Policy\" requiring security team approval when critical vulnerabilities are detected\n\n### Custom SAST Ruleset Configuration\n\nCreate `.gitlab\u002Fsast-ruleset.toml` to customize analyzer behavior:\n\n```toml\n[semgrep]\n  [[semgrep.ruleset]]\n    dirs = [\"src\"]\n\n  [[semgrep.passthrough]]\n    type = \"url\"\n    target = \"\u002Fsgrep-rules\u002Fcustom-rules.yml\"\n    value = \"https:\u002F\u002Fsemgrep.dev\u002Fp\u002Fowasp-top-ten\"\n\n  [[semgrep.passthrough]]\n    type = \"url\"\n    target = \"\u002Fsgrep-rules\u002Fjava-rules.yml\"\n    value = \"https:\u002F\u002Fsemgrep.dev\u002Fp\u002Fjava\"\n```\n\n## Security Dashboard and Vulnerability Management\n\n### Vulnerability Report\n\nGitLab consolidates all scanner findings into a single Vulnerability Report accessible at Security & Compliance > Vulnerability Report. Each vulnerability includes:\n- Severity rating (Critical, High, Medium, Low, Info)\n- Scanner source (SAST, DAST, Container, Dependency, Secret)\n- Location in source code or image layer\n- Remediation guidance and suggested fixes\n- Status tracking (Detected, Confirmed, Dismissed, Resolved)\n\n### Merge Request Security Widget\n\nEvery merge request displays a security scanning widget showing:\n- New vulnerabilities introduced by the MR\n- Fixed vulnerabilities resolved by the MR\n- Comparison against the target branch baseline\n\n## Pipeline Optimization\n\n- **Parallel execution**: Security scanners run concurrently in the security stage\n- **Caching**: Use CI cache for dependency downloads to speed up scanning\n- **Incremental scanning**: SAST can scan only changed files using `SAST_INCREMENTAL: \"true\"`\n- **Fail conditions**: Set `allow_failure: false` on critical scanners to enforce quality gates\n\n## Monitoring and Metrics\n\n| Metric | Description | Target |\n|--------|-------------|--------|\n| Pipeline security coverage | Percentage of projects with all scanners enabled | > 95% |\n| Critical vulnerability MTTR | Time from detection to resolution for critical findings | \u003C 48 hours |\n| False positive rate | Percentage of dismissed-as-false-positive findings | \u003C 15% |\n| Secret detection block rate | Percentage of secret commits blocked by push rules | > 99% |\n\n## References\n\n- [GitLab Security Scanning Documentation](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002F)\n- [GitLab SAST Analyzers](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fsast\u002F)\n- [GitLab DAST Configuration](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fdast\u002F)\n- [GitLab Security Policies](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fpolicies\u002F)\n- [GitLab Vulnerability Management](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fvulnerability_report\u002F)\n","# Building DevSecOps Pipeline with GitLab CI\n\n## Overview\n\nGitLab provides an integrated DevSecOps platform that embeds security testing directly into the CI\u002FCD pipeline. By leveraging GitLab's built-in security scanners---SAST, DAST, container scanning, dependency scanning, secret detection, and license compliance---teams can shift security left, catching vulnerabilities during development rather than post-deployment. GitLab Duo AI assists with false positive detection for SAST vulnerabilities, helping security teams focus on genuine issues.\n\n\n## When to Use\n\n- When deploying or configuring building devsecops pipeline with gitlab ci capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- GitLab Ultimate license (required for full security scanner suite)\n- GitLab Runner configured (shared or self-hosted)\n- `.gitlab-ci.yml` pipeline configuration familiarity\n- Docker-in-Docker (DinD) or Kaniko for container builds\n- Application deployed to a staging environment for DAST scanning\n\n## Core Security Scanning Stages\n\n### Static Application Security Testing (SAST)\n\nSAST analyzes source code for vulnerabilities before compilation. GitLab supports 14+ languages using analyzers such as Semgrep, SpotBugs, Gosec, Bandit, and NodeJsScan. The simplest inclusion uses GitLab's managed templates.\n\n### Dynamic Application Security Testing (DAST)\n\nDAST tests running applications by simulating attack payloads against HTTP endpoints. It detects XSS, SQLi, CSRF, and other runtime vulnerabilities that static analysis cannot find. DAST requires a deployed, accessible target URL.\n\n### Container Scanning\n\nUses Trivy to scan Docker images for known CVEs in OS packages and application dependencies. Runs after the Docker build stage to gate images before they reach a registry.\n\n### Dependency Scanning\n\nInspects dependency manifests (package.json, requirements.txt, pom.xml, Gemfile.lock) for known vulnerable versions. Operates at the source code level, complementing container scanning.\n\n### Secret Detection\n\nScans commits for accidentally committed credentials, API keys, tokens, and private keys using pattern matching and entropy analysis. Runs on every commit to prevent secrets from reaching the repository.\n\n## Implementation\n\n### Complete Pipeline Configuration\n\n```yaml\n# .gitlab-ci.yml\n\nstages:\n  - build\n  - test\n  - security\n  - deploy-staging\n  - dast\n  - deploy-production\n\nvariables:\n  DOCKER_IMAGE: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA\n  SECURE_LOG_LEVEL: \"info\"\n\n# Include GitLab managed security templates\ninclude:\n  - template: Security\u002FSAST.gitlab-ci.yml\n  - template: Security\u002FSecret-Detection.gitlab-ci.yml\n  - template: Security\u002FDependency-Scanning.gitlab-ci.yml\n  - template: Security\u002FContainer-Scanning.gitlab-ci.yml\n  - template: DAST.gitlab-ci.yml\n  - template: Security\u002FLicense-Scanning.gitlab-ci.yml\n\nbuild:\n  stage: build\n  image: docker:24.0\n  services:\n    - docker:24.0-dind\n  variables:\n    DOCKER_TLS_CERTDIR: \"\u002Fcerts\"\n  script:\n    - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY\n    - docker build -t $DOCKER_IMAGE .\n    - docker push $DOCKER_IMAGE\n  rules:\n    - if: $CI_COMMIT_BRANCH\n\nunit-tests:\n  stage: test\n  image: $DOCKER_IMAGE\n  script:\n    - npm ci\n    - npm run test:coverage\n  coverage: '\u002FLines\\s*:\\s*(\\d+\\.?\\d*)%\u002F'\n  artifacts:\n    reports:\n      junit: junit-report.xml\n      coverage_report:\n        coverage_format: cobertura\n        path: coverage\u002Fcobertura-coverage.xml\n\n# Override SAST to run in security stage\nsast:\n  stage: security\n  variables:\n    SAST_EXCLUDED_PATHS: \"spec,test,tests,tmp,node_modules\"\n    SEARCH_MAX_DEPTH: 10\n\n# Override container scanning\ncontainer_scanning:\n  stage: security\n  variables:\n    CS_IMAGE: $DOCKER_IMAGE\n    CS_SEVERITY_THRESHOLD: \"HIGH\"\n\n# Override dependency scanning\ndependency_scanning:\n  stage: security\n\n# Override secret detection\nsecret_detection:\n  stage: security\n\n# License compliance scanning\nlicense_scanning:\n  stage: security\n\ndeploy-staging:\n  stage: deploy-staging\n  image: bitnami\u002Fkubectl:latest\n  script:\n    - kubectl set image deployment\u002Fapp app=$DOCKER_IMAGE -n staging\n    - kubectl rollout status deployment\u002Fapp -n staging --timeout=300s\n  environment:\n    name: staging\n    url: https:\u002F\u002Fstaging.example.com\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\n# DAST runs against deployed staging\ndast:\n  stage: dast\n  variables:\n    DAST_WEBSITE: https:\u002F\u002Fstaging.example.com\n    DAST_FULL_SCAN_ENABLED: \"true\"\n    DAST_BROWSER_SCAN: \"true\"\n  needs:\n    - deploy-staging\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\ndeploy-production:\n  stage: deploy-production\n  image: bitnami\u002Fkubectl:latest\n  script:\n    - kubectl set image deployment\u002Fapp app=$DOCKER_IMAGE -n production\n    - kubectl rollout status deployment\u002Fapp -n production --timeout=300s\n  environment:\n    name: production\n    url: https:\u002F\u002Fapp.example.com\n  when: manual\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n```\n\n### Security Approval Policies\n\nConfigure scan execution policies to enforce mandatory security scans:\n\n1. Navigate to Security & Compliance > Policies\n2. Create a \"Scan Execution Policy\" requiring SAST and secret detection on all branches\n3. Create a \"Merge Request Approval Policy\" requiring security team approval when critical vulnerabilities are detected\n\n### Custom SAST Ruleset Configuration\n\nCreate `.gitlab\u002Fsast-ruleset.toml` to customize analyzer behavior:\n\n```toml\n[semgrep]\n  [[semgrep.ruleset]]\n    dirs = [\"src\"]\n\n  [[semgrep.passthrough]]\n    type = \"url\"\n    target = \"\u002Fsgrep-rules\u002Fcustom-rules.yml\"\n    value = \"https:\u002F\u002Fsemgrep.dev\u002Fp\u002Fowasp-top-ten\"\n\n  [[semgrep.passthrough]]\n    type = \"url\"\n    target = \"\u002Fsgrep-rules\u002Fjava-rules.yml\"\n    value = \"https:\u002F\u002Fsemgrep.dev\u002Fp\u002Fjava\"\n```\n\n## Security Dashboard and Vulnerability Management\n\n### Vulnerability Report\n\nGitLab consolidates all scanner findings into a single Vulnerability Report accessible at Security & Compliance > Vulnerability Report. Each vulnerability includes:\n- Severity rating (Critical, High, Medium, Low, Info)\n- Scanner source (SAST, DAST, Container, Dependency, Secret)\n- Location in source code or image layer\n- Remediation guidance and suggested fixes\n- Status tracking (Detected, Confirmed, Dismissed, Resolved)\n\n### Merge Request Security Widget\n\nEvery merge request displays a security scanning widget showing:\n- New vulnerabilities introduced by the MR\n- Fixed vulnerabilities resolved by the MR\n- Comparison against the target branch baseline\n\n## Pipeline Optimization\n\n- **Parallel execution**: Security scanners run concurrently in the security stage\n- **Caching**: Use CI cache for dependency downloads to speed up scanning\n- **Incremental scanning**: SAST can scan only changed files using `SAST_INCREMENTAL: \"true\"`\n- **Fail conditions**: Set `allow_failure: false` on critical scanners to enforce quality gates\n\n## Monitoring and Metrics\n\n| Metric | Description | Target |\n|--------|-------------|--------|\n| Pipeline security coverage | Percentage of projects with all scanners enabled | > 95% |\n| Critical vulnerability MTTR | Time from detection to resolution for critical findings | \u003C 48 hours |\n| False positive rate | Percentage of dismissed-as-false-positive findings | \u003C 15% |\n| Secret detection block rate | Percentage of secret commits blocked by push rules | > 99% |\n\n## References\n\n- [GitLab Security Scanning Documentation](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002F)\n- [GitLab SAST Analyzers](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fsast\u002F)\n- [GitLab DAST Configuration](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fdast\u002F)\n- [GitLab Security Policies](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fpolicies\u002F)\n- [GitLab Vulnerability Management](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fvulnerability_report\u002F)\n",{"name":5,"tags":25,"author":34,"domain":35,"source":36,"license":15,"version":37,"nist_csf":38,"subdomain":27,"description":7,"mitre_attack":43,"source_commit":49},[26,27,28,29,30,31,32,33],"gitlab-ci","devsecops","sast","dast","container-scanning","dependency-scanning","secret-detection","cicd-security","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[39,40,41,42],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04",[44,45,46,47,48],"T1195.001","T1195.002","T1552.001","T1190","T1610","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill building-devsecops-pipeline-with-gitlab-ci",{"tool":66,"command":67},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill building-devsecops-pipeline-with-gitlab-ci",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill building-devsecops-pipeline-with-gitlab-ci","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002FSKILL.md",true,[74,80,84,90,94,98,104],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Ftemplate.md","ASSET","资产文件",1423,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Fassets\u002Ftemplate.md",{"path":81,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fapi-reference.md","REFERENCE","参考文档",1544,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Freferences\u002Fapi-reference.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fstandards.md",2662,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Freferences\u002Fstandards.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fworkflows.md",2327,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Freferences\u002Fworkflows.md",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fagent.py","SCRIPT","脚本",4951,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Fscripts\u002Fagent.py",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fprocess.py",6111,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Fscripts\u002Fprocess.py",[109,117,124,132,140,148],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":149,"name":150,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]