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 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/pipeline-design)<a href="https://agentmods.dev/skills/niels-emmer/myace/pipeline-design"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/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/pipeline-design"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/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.00035 | $0.00562 |
| Opus 5 | $0.00017 | $0.00281 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
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 9d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
A CI/CD pipeline is the release path for every change — if it's slow, flaky, or unsafe, every deploy inherits that. This skill is the checklist for designing pipelines that promote immutable artifacts through environments with gates that actually protect production.
When to use it
When designing or modifying a pipeline: a new workflow, a new environment, a change to promotion rules, or a pipeline that's become a bottleneck or a source of flakiness.
Steps / checklist
- Pipeline as code. Pipeline definitions are version-controlled alongside the application. No manual steps in a deployment process — a manual step is a bug to automate.
- Stage isolation. Each stage (build → unit test → integration test → staging deploy → smoke test → prod deploy) runs in a clean environment with the artifacts it needs. Stages don't share mutable state.
- Immutable artifacts. Every build produces a versioned, immutable artifact (container image, binary, package) promoted through environments without rebuilding. Never rebuild from source for a deployment — promote the same artifact that passed tests.
- Environment gates. Every promotion between environments requires passing the previous stage's gates. A failed gate stops the promotion — no force-promoting around a red stage.
- Rollback over fix-forward. Rollback must be faster than fix-forward for production issues. Prefer deploying the previous known-good artifact over patching forward under pressure.
- Secret injection. Secrets are injected at deploy time from a secrets manager, scoped to the job that needs them. Never bake secrets into artifacts or pipeline config.
- Caching and speed. Cache dependencies and build layers where safe, but never cache in a way that makes builds non-reproducible. A pipeline nobody waits for is a pipeline that gets bypassed.
- Failure visibility. Pipeline failures page the right people with the right context. A red pipeline that nobody notices is worse than no pipeline.
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.
- 9d ago First seen · 30 lines · 35 tokens per session scan A 5eeac90132fa
Pipeline Design is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 562 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-09-03.
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.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.