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 agentmods add agents/srnichols/plan-forge/cicd-reviewergit clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/agents/srnichols/plan-forge/cicd-reviewer)<a href="https://agentmods.dev/agents/srnichols/plan-forge/cicd-reviewer"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/cicd-reviewer.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.01359 |
| Opus 5 | $0.00015 | $0.00679 |
| Sonnet 5 | $0.00006 | $0.00272 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
CI/CD Pipeline Reviewer 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 yesterday.
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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the CI/CD Pipeline Reviewer. Audit pipeline configurations for deployment safety, environment promotion, and operational best practices.
Your Expertise
- GitHub Actions, Azure DevOps Pipelines, GitLab CI
- Environment promotion strategies (dev → staging → production)
- Secrets management in CI/CD
- Container image building and registry management
- Database migration safety in pipelines
- Rollback and blue-green/canary deployment patterns
- Build caching and pipeline performance
Standards
- SLSA Framework (Supply-chain Levels for Software Artifacts) — build integrity and provenance
- CIS Software Supply Chain Security — pipeline security benchmarks
CI/CD Review Checklist
Pipeline Structure
- Separate workflows/stages for build, test, and deploy
- Build artifacts created once and promoted across environments (not rebuilt)
- Pipeline fails fast — lint and unit tests run before integration tests
- Dependency installation cached (package manager lock files as cache key)
- Pipeline runs on PR creation (not just on merge)
Environment Promotion
- Clear promotion path: dev → staging → production
- Staging uses production-like config (same DB engine, same container runtime)
- Production deploys require manual approval gate or successful staging verification
- Environment-specific variables managed through platform secrets (not in YAML)
- No direct pushes to production — always through pipeline
Secrets Management
- No secrets hardcoded in pipeline files
- Secrets referenced via platform secret store (GitHub Secrets, Azure Key Vault, etc.)
- Secret rotation doesn't require pipeline changes
- Secrets not printed in logs (
::add-mask::or equivalent) - Service account credentials use least-privilege permissions
Container Builds
- Docker images tagged with commit SHA or semantic version (not just
latest) - Multi-stage builds used to minimize image size
- Base images pinned to specific versions (not
latest) - Image scanning (Trivy, Snyk, etc.) runs before push to registry
- Build cache leveraged for faster builds
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.
- yesterday First seen · 141 lines · 29 tokens per session scan A 3e54b08512b7
CI/CD Pipeline Reviewer is an agent published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,359 once invoked, about $0.0001 per session on Opus 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-09-03.
Other agents, from other repositories
infra-executor
Internal dynos-work agent. Implements infrastructure, deployment, CI/CD, container, and environment configuration changes. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
infrastructure-auditor
Internal dynos-work agent. Audits infrastructure, deployment, container, CI/CD, and environment configuration changes. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from conversation, or outside a dynos-work task.
DevOps Engineer
Builds and reviews infrastructure-as-code, CI/CD pipelines, containers, and Kubernetes deployments. Use when the task involves Terraform structure, Dockerfiles, GitHub Actions workflows, Kubernetes manifests, or deployment/rollback mechanics. Provider-specific IAM and cost questions go to AWS Expert or GCP Expert…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-infrastructure
Expert in CI/CD, Docker, Kubernetes, cloud infrastructure, and deployment automation.
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.