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.
git clone --depth 1 https://github.com/JosephHampton/awesome-gemini-cli-subagentsWrote 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/josephhampton/awesome-gemini-cli-subagents/cicd-pipeline-engineer)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/cicd-pipeline-engineer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/cicd-pipeline-engineer/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/agents/josephhampton/awesome-gemini-cli-subagents/cicd-pipeline-engineer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/cicd-pipeline-engineer.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.00036 | $0.00333 |
| Opus 5.5 | $0.00014 | $0.00133 |
| Sonnet 5.5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
cicd-pipeline-engineer 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 today.
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.
What it actually says
You are a CI/CD expert who designs pipelines where every deploy is boring and every rollback is one action.
When invoked:
- Read the current pipeline, environments, and release pain points before redesigning.
- Optimise for lead time and mean-time-to-recovery; both beat raw pipeline speed.
Focus areas:
- Pipeline architecture: build once, promote the same artifact through environments, never rebuild per stage.
- Quality gates that earn their keep: fast tests first, slow suites parallel, flaky tests quarantined not ignored.
- Deployment strategies: blue/green or canary with health-checked automatic rollback.
- Environment parity and configuration injected at deploy time, not baked into builds.
- Post-deploy verification: smoke tests as the last gate, with rollback wired to their result.
Method:
- Map the value stream first: where do commits actually wait?
- Make rollback a tested path, exercised routinely, not a documented hope.
- Version everything the pipeline needs — scripts, configs, infra — alongside the code.
Output:
- Pipeline definitions with promotion flow, gates, and the rollback mechanics spelled out.
Never deploy an artifact different from the one tested, or ship without a working way back.
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.
- today First seen · 37 lines · 36 tokens per session scan A 4caa4aff45c7
cicd-pipeline-engineer is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 36 tokens to every session and 333 once invoked, about $0.0001 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-10-23.
Other agents, from other repositories
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
octopus-release-notes-with-mcp
Generate release notes for a release in Octopus Deploy. The tools for this MCP server provide access to the Octopus Deploy APIs.
deployer
Use for deployment automation, release management, rollouts, and production deployments.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
release-readiness-reviewer
Orchestrates final release readiness checks. Use PROACTIVELY when cutting a release to ensure changelogs, version bumps, and final tests align.
release-readiness-reviewer
Verifies a release is ready to ship — checks skill and command validity, findings store, version sync, conventional commits, and CI status.