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 orlando-japan/claude-code-setting --skill ci-pipeline-designgit clone --depth 1 https://github.com/orlando-japan/claude-code-settingWrote 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/orlando-japan/claude-code-setting/ci-pipeline-design)<a href="https://agentmods.dev/skills/orlando-japan/claude-code-setting/ci-pipeline-design"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/ci-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/orlando-japan/claude-code-setting/ci-pipeline-design"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/ci-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.00032 | $0.01061 |
| Opus 5 | $0.00016 | $0.00531 |
| Sonnet 5 | $0.00006 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
ci-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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI pipeline design
Two failure modes dominate bad CI:
- Slow. Devs wait 30 min for feedback and lose flow.
- Flaky. Devs learn to "just rerun" and stop trusting results.
Fix both or fix neither — a reliable slow pipeline is ignored; a fast unreliable one is worse.
Stages, in order
- Lint + type check. Fastest, cheapest, catches the most trivial mistakes. Run first, fail fast.
- Unit tests. Fast, deterministic, no I/O.
- Integration tests. Hit real DBs, real HTTP. Slower, but catch wiring bugs unit tests miss.
- Build artifacts. Compile, bundle, produce the deployable.
- E2E tests. Full stack. Slow and brittle; reserve for critical flows.
- Security / lint deep passes.
npm audit,pip-audit, secret scanning, license check. - Deploy (if the branch is deploy-able).
Later stages depend on earlier stages passing. Fail fast at the earliest stage possible.
Parallelism and caching
Cache aggressively
- Dependency cache (
node_modules,~/.cache/pip,~/.cargo). Keyed by lockfile hash. - Build cache. If nothing changed in a subsystem, don't rebuild it.
- Test result cache. If the tests' inputs (code + deps) haven't changed, the results haven't either. Some test runners support this natively (Bazel, Turborepo, Nx).
- Docker layer cache. Order Dockerfile commands from "rarely changes" to "often changes."
Parallelize independent work
- Lint and unit tests don't depend on each other — run in parallel.
- Integration tests by service shard — multiple runners in parallel.
- E2E scenarios split across machines — fan out.
Know the critical path
The CI pipeline's wall-clock duration = the longest chain of sequential steps. Reducing a non-critical-path step doesn't help. Profile the pipeline itself: where is time actually spent?
Reliability
- No network calls to the internet from tests unless explicitly mocked. Network flakes destroy trust.
- No retries on test failure. Retries hide real bugs. Fix flaky tests.
- Isolated environments per run. No shared DB, no shared temp files, no shared caches that could interfere.
- Deterministic order. No tests that depend on the previous test's state.
- Bounded timeouts. Per-step timeouts so a hung process doesn't burn an hour.
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 · 105 lines · 32 tokens per session scan A 054573e0d33c
ci-pipeline-design is a skill published in the GitHub repository orlando-japan/claude-code-setting (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 1,061 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-31.
Other skills, from other repositories
Test Automation
Patterns for keeping the test suite fast, deterministic, and runnable in CI — mocking rules, isolation, and flakiness prevention.
deploy
Use when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked. Push always requires explicit confirmation. Trigger with /hyperflow:deploy, "ship it", "ready to push", "release", "cut a release", "deploy".
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.
Code Coverage Analysis
Measure and enforce test coverage with Istanbul/nyc, c8, Jest, and Vitest. Covers branch versus line coverage, per-directory thresholds, CI gates, and correctly excluding generated code from reports.
smoke-test
Post-deploy health-check against a live URL. Validates HTTP status, response content, and critical endpoints. Runnable standalone OR as the final step of the deploy skill.