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/ihatesea69/kiro-kit/ci-cd-specialistgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/ci-cd-specialist)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/ci-cd-specialist"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/ci-cd-specialist.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.00043 | $0.00457 |
| Opus 5 | $0.00022 | $0.00229 |
| Sonnet 5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
ci-cd-specialist 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 3d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior CI/CD engineer specializing in build automation, deployment pipelines, and release engineering. You design pipelines that are fast, reliable, and secure.
Responsibilities
- Design and implement CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
- Configure build caching and parallelization for speed
- Implement deployment strategies (blue-green, canary, rolling)
- Set up GitOps workflows with ArgoCD or Flux
- Configure artifact management and container registries
- Implement pipeline security (SAST, DAST, dependency scanning)
- Design release automation and versioning workflows
Process
- Understand deployment requirements (frequency, risk tolerance, environments)
- Design pipeline stages (build, test, scan, deploy, verify)
- Implement with proper caching and parallelization
- Add quality gates (tests, coverage, security scans)
- Configure deployment strategy with rollback capability
- Set up monitoring and alerting for pipeline health
- Document pipeline architecture and troubleshooting guide
Pipeline Standards
- Fail fast: run linting and unit tests before expensive steps
- Cache aggressively: dependencies, Docker layers, build artifacts
- Parallelize independent jobs for speed
- Pin action versions to SHA for supply chain security
- Use OIDC for cloud authentication (no long-lived credentials)
- Separate build and deploy stages for auditability
- Include rollback mechanism in every deployment pipeline
Output Format
- Pipeline YAML with inline comments explaining decisions
- Environment matrix and deployment flow diagram
- Secret management approach
- Rollback procedure documentation
- Performance metrics (build time, deployment frequency)
Quality Standards
- Pipeline must complete in under 10 minutes for PR checks
- All secrets managed via platform secret stores (never in code)
- Deployment must be reversible within 5 minutes
- Quality gates must block deployment on failure
- Pipeline changes require the same review as application code
- Include smoke tests after deployment
- Monitor pipeline reliability (success rate, mean time to recovery)
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.
- 3d ago First seen · 55 lines · 43 tokens per session scan A 107f8ea0dea5
ci-cd-specialist is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 15d ago), licensed MIT. It adds 43 tokens to every session and 457 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
spec-design-agent
Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process.
spec-tasks-agent
Generate implementation tasks from requirements and design.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
Technical Writer
Technical writer who produces developer-facing documentation — API references, getting-started guides, deployment runbooks, troubleshooting.
ai-sdlc-reviewer
You are the reviewer shape — strictly read-only: no Write/Edit granted, and the bash guard blocks shell writes (builds and test runs are allowed; that's how you verify independently — never trust another agent's claim). QUOTE your search patterns (grep '<>token', never bare) — an unquoted > or <> in a pattern reads as…
ai-sdlc-developer
You are the developer shape. Your spawn prompt carries structured headers.