Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add fortify/skills --skill fortify-cicd-integrationgit clone --depth 1 https://github.com/fortify/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/fortify/skills/fortify-cicd-integration)<a href="https://agentmods.dev/skills/fortify/skills/fortify-cicd-integration"><img src="https://agentmods.dev/badge/skills/fortify/skills/fortify-cicd-integration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fortify/skills/fortify-cicd-integration"><img src="https://agentmods.dev/badge/skills/fortify/skills/fortify-cicd-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.01752 |
| Opus 5.5 | $0.00020 | $0.00701 |
| Sonnet 5.5 | $0.00010 | $0.00350 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
fortify-cicd-integration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fortify CI/CD Integration
Step 1: Investigate the repository first
Before asking the user anything or generating output, inspect the repository to determine context automatically.
Detect the CI/CD platform
Look for these platform-specific files (check root and common subdirectories):
| Path / file | Platform |
|---|---|
.github/workflows/*.yml |
GitHub Actions |
.gitlab-ci.yml |
GitLab CI |
azure-pipelines.yml |
Azure DevOps |
Jenkinsfile |
Jenkins |
bitbucket-pipelines.yml |
Bitbucket Pipelines → generic fcli ci |
.travis.yml |
Travis CI → generic fcli ci |
.circleci/config.yml |
CircleCI → generic fcli ci |
teamcity-settings.kts or .teamcity/ |
TeamCity → generic fcli ci |
.buildkite/pipeline.yml |
Buildkite → generic fcli ci |
bamboo-specs/ |
Bamboo → generic fcli ci |
If multiple are present, note all of them and generate for whichever the user's request implies (or ask if ambiguous).
If no known platform file is found, use the generic fcli ci action approach — see references/generic-ci-ssc.md for the SSC case or references/generic-ci-fod.md for the FoD case.
Detect the build tool and language
Check in this priority order:
- Existing CI/CD config files — read the platform's existing workflow/pipeline files to find setup steps already in use. Extract the exact toolchain and version already specified — use these verbatim so the Fortify workflow matches the project's existing build environment.
- Build manifest files — use the presence of files such as
requirements.txt,pom.xml,build.gradle,package.json,*.csproj,go.mod, etc. to identify the language and build tooling required. Ensure the generated Fortify workflow includes any setup steps needed to successfully build the project with that toolchain. Refer to the platform-specific guidance file for the correct setup action/step syntax.
Check for an existing Fortify configuration
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 137 lines · 49 tokens per session scan A d9af1f889d2e
fortify-cicd-integration is a skill published in the GitHub repository fortify/skills (23 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 1,752 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
ai-agents-generation-and-release
Operate the ai-agents generation and release machinery, covering the seven buildall.py generators, generateagents.py, the drift gates, the version-free plugin manifests, and the npm publish path. Use when you say regenerate the mirrors, run the drift checks, why is the plugin version gate red, release the npm cli. Do…
ai-agents-research-methodology
How a hunch becomes an accepted result in this repo. Covers the evidence bar, hypothesis-predicts-numbers discipline, and the idea lifecycle from contradiction log through probe, eval baseline, ADR debate, calibrated gate, and post-ship monitoring. Use when you say how do I prove this idea, run the idea lifecycle…
buy-vs-build-framework
Strategic framework for evaluating build, buy, partner, or defer decisions with four-phase process, tiered TCO analysis, and integration with decision quality tools. Use for strategic build/buy/partner/defer with TCO. Do NOT use for "is there an existing library for this" (use programming-advisor).
cva-analysis
Systematic abstraction discovery using Commonality Variability Analysis. Build matrix of what varies vs what's constant, then let patterns emerge. Prevents wrong abstractions by deferring pattern selection until requirements are analyzed. Use when facing multiple similar requirements and need to discover natural…