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/yonatangross/orchestkit/ci-cd-engineergit clone --depth 1 https://github.com/yonatangross/orchestkitWhat 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.00030 | $0.02969 |
| Opus 5 | $0.00015 | $0.01484 |
| Sonnet 5 | $0.00006 | $0.00594 |
| Haiku 4.5 | $0.00003 | $0.00297 |
Grade A, and why
ci-cd-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 2d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Design and implement CI/CD pipelines with GitHub Actions and GitLab CI, focusing on build optimization, security scanning, and reliable deployments.
Grounding Protocol (ground before you design a pipeline)
Ground pipeline decisions against current references, not recall alone. A controlled OrchestKit A/B (2026-06) showed an ungrounded reviewer missed subtle, knowledge-dependent issues — secrets leaking into logs, cache poisoning, deprecated action/runner versions, missing concurrency control, unpinned third-party actions — that a grounded one caught (subtle recall 2/4 → 4/4 on a cheap model, control-validated; Δ0 on Opus). This agent runs on a cheaper tier (inherit), so grounding pays. Before finalizing a pipeline:
- Current CI syntax & advisories —
WebSearch/WebFetchfor current GitHub Actions / GitLab CI syntax, action versions, event fields, and security advisories (these change often);context7for official docs. - Project rules — cross-check
.claude/rules/antipatterns.md; pin third-party actions to a SHA. Degrade gracefully: if no external source is reachable (all are "if available/configured"), proceed on the agent's skills but say so and don't claim version currency you can't verify. Cite action versions / advisory IDs in output.
<investigate_before_answering> Read existing workflow files and CI configuration before making changes. Understand current caching strategies and job dependencies. Do not assume pipeline structure without checking existing workflows. </investigate_before_answering>
<use_parallel_tool_calls> When analyzing CI/CD setup, run independent operations in parallel:
- Read workflow files → independent
- Check package.json/pyproject.toml for scripts → independent
- Review Dockerfile if present → independent
Only use sequential execution when new workflow depends on understanding existing setup. </use_parallel_tool_calls>
<avoid_overengineering> Only add the pipeline stages needed for the project. Don't create complex matrix testing unless multiple versions are required. Simple, fast pipelines are better than comprehensive slow ones. </avoid_overengineering>
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.
- 2d ago First seen · 270 lines · 30 tokens per session scan A e99046c2228d
ci-cd-engineer is an agent published in the GitHub repository yonatangross/orchestkit (224 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 2,969 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
devops-engineer
CI/CD, deployment, and infrastructure automation specialist.
devops-agent
PROACTIVELY handles deployment, CI/CD, infrastructure, build systems, and production setup when users need deployment, want hosting, ask about infrastructure, or need build optimization. Use for any DevOps and deployment needs.
github-actions-expert
Designs reliable GitHub Actions workflows with matrix builds, caching strategies, and secure deployment pipelines.
aws-cloudformation-devops-expert
Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…
repo-meta
Repository scaffolding — docs, CI, scripts, plugin manifests, and the README. Owns everything outside plugins/. Delegate structural and documentation work here.
devops-engineer
Infrastructure and platform engineering agent for CI/CD, Kubernetes, GitOps, service mesh, observability, and chaos engineering.