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 skills/int2t05/engineering-skills/ci-cdnpx skills add int2t05/engineering-skills --skill ci-cdgit clone --depth 1 https://github.com/int2t05/engineering-skillsWrote 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/int2t05/engineering-skills/ci-cd)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/ci-cd"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/ci-cd.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.01622 |
| Opus 5 | $0.00031 | $0.00811 |
| Sonnet 5 | $0.00012 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
ci-cd 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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD and Automation
Automate quality gates so no change reaches production without passing tests, lint, type checking, and build. CI/CD is the enforcement mechanism for every other skill — it catches what humans and agents miss, and it does so consistently on every change.
Shift left: catch problems as early in the pipeline as possible. A bug caught in linting costs minutes; the same bug caught in production costs hours. A deployment with 3 changes is easier to debug than one with 30.
When to use
- Setting up a new project's CI pipeline.
- Adding or modifying automated checks (lint, types, tests, build, audit).
- Configuring deployment pipelines or deployment strategies.
- Debugging CI failures.
- When a change should trigger automated verification.
Not for: debugging runtime bugs (use debugging); production launch strategy and rollback (use shipping); routine commits (use git-workflow).
Steps
1. Define the quality gate pipeline
Every change goes through these gates before merge — no gate can be skipped. If lint fails, fix lint (don't disable the rule). If a test fails, fix the code (don't skip the test).
Pull Request
│
▼
LINT → code style + static analysis
TYPE CHECK → type safety (typed languages only)
UNIT TESTS → behavior
BUILD → artifact compiles / bundles
INTEGRATION → API/DB tests against real deps
E2E (opt.) → full user journeys in a browser/app
SECURITY → dependency + secret scan
│
▼
Ready for review
Detect the stack from its manifest, then map each gate to the right command — never assume npm test:
| Stack | Manifest | Lint | Test | Build |
|---|---|---|---|---|
| Node / TS | package.json |
eslint / prettier | npm test (jest/vitest) | npm run build |
| Python | pyproject.toml |
ruff / mypy | pytest | pip build / uv build |
| Go | go.mod |
go vet / golangci-lint | go test ./... | go build |
| Rust | Cargo.toml |
clippy | cargo test | cargo build --release |
| Java | pom.xml / build.gradle |
spotbugs / checkstyle | mvn test / gradle test | mvn package / gradle build |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 123 lines · 62 tokens per session scan A bedffe42a3ca
ci-cd is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 1,622 once invoked, about $0.0003 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-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
test-first
Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.
plan-create
Create structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users…
specify-incremental
Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over factory automation.