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 niels-emmer/myace --skill ci-cd-pipeline-designgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/ci-cd-pipeline-design)<a href="https://agentmods.dev/skills/niels-emmer/myace/ci-cd-pipeline-design"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/ci-cd-pipeline-design/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/niels-emmer/myace/ci-cd-pipeline-design"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/ci-cd-pipeline-design.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.00024 | $0.00284 |
| Opus 5 | $0.00012 | $0.00142 |
| Sonnet 5 | $0.00005 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
CI/CD Pipeline Design 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 11d 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.
What it actually says
Purpose
Design pipelines that are safe, fast, and auditable.
Checklist
- Stage isolation: each stage (build, test, deploy) runs independently; failure in one doesn't cascade.
- Caching: dependency caches are content-addressed and invalidated on lockfile changes.
- Secret injection: secrets come from a secrets manager at runtime, not from repo variables or baked-in.
- Artifact promotion: same binary/image promoted through environments — never rebuild for staging/prod.
- Rollback: production rollback is a one-click or one-command operation, tested regularly.
- Gate conditions: each environment requires the previous stage's tests to pass before proceeding.
- Notifications: pipeline failures notify the owning team with relevant context (commit, stage, logs).
Expected output
A pipeline definition where each stage is independently verifiable, artifacts are immutable, and production rollback is faster than fix-forward.
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.
- 11d ago First seen · 26 lines · 24 tokens per session scan A b74aea919829
CI/CD Pipeline Design is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 284 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-08-31.
Other skills, from other repositories
loom-ci-cd
Designs and implements CI/CD pipelines for automated testing, builds, deployment, and security scanning.
keel
Measure whether a codebase's verification actually touches the world, or whether it is checking itself. Keel gathers the verification edges it can read in a target (GitHub Actions, CircleCI, GitLab CI, Travis, package scripts, Makefile, Rakefile, pyproject and a dozen tool configs) — and reports the surfaces it…
pre-merge
The CI gate. Takes a feature branch from "eng says done" to "PR open against staging with green checks". Runs the project's preflight-resolved pipeline from devkit/policy.json components[]: sync → parallel correctness + security waves → coverage → regression tail → security/migration → PRD-consistency → open PR. Emits…
merge
The ship gate — the only skill that merges. --staging merges the feature→staging PR on green CI, deploys, verifies, emits a human test script and stamps the staging sign-off on approval. --production ships the double-confirmed release to main and deploys production. Never self-certifies staging; nothing reaches main…
loom-fluxcd
GitOps continuous delivery toolkit for Kubernetes with Flux CD.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.