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 martian56/claude-engineer --skill ci-cd-pipelinegit clone --depth 1 https://github.com/martian56/claude-engineerWrote 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/martian56/claude-engineer/ci-cd-pipeline)<a href="https://agentmods.dev/skills/martian56/claude-engineer/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/martian56/claude-engineer/ci-cd-pipeline/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/martian56/claude-engineer/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/martian56/claude-engineer/ci-cd-pipeline.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.00064 | $0.00483 |
| Opus 5 | $0.00032 | $0.00242 |
| Sonnet 5 | $0.00013 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
ci-cd-pipeline 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.
What it actually says
CI/CD Pipeline
Announce at start: "I'm using claude-engineer:ci-cd-pipeline to generate CI and containerization."
Finish line
CI-green + container-ready. No actual deploy. (Deploy targets/credentials are out of scope for v1.)
What to generate
- GitHub Actions - a polyglot workflow that, on PR and main:
- installs both toolchains (uv for Python, pnpm/Bun for JS) with caching;
- lint (
ruff+eslint/prettier --check); - typecheck (
mypy/pyright+tsc --noEmit); - test (
pytest+vitest run --coverage) using service containers (Postgres/Redis) for integration tests; - build (frontend build + backend image build);
- run the four quality gates (
claude-engineer:testing-and-quality) as the merge condition.
- Multi-stage Dockerfiles - FastAPI (uv builder → slim runtime) and the frontend (Next
output: standaloneor static build) +.dockerignore. These prove the app is container-ready.
Non-negotiables
- CI enforces the same four gates the local commit gate enforces - no weaker checks in CI.
- Caching for both toolchains (don't reinstall the world each run).
- Pin action versions and base images.
Full detail (the complete Actions workflow, service-container config, the multi-stage Dockerfiles, prod compose notes):
read references/ci-and-containers.md on demand.
Red flags - STOP
- CI that skips a gate the local gate enforces.
- A Dockerfile that copies
.env/secrets ornode_modules/.venv(use.dockerignore). - Unpinned
latestactions or base images.
What ships with it
1 file 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.
- 9d ago First seen · 35 lines · 64 tokens per session scan A e258bdb77286
ci-cd-pipeline is a skill published in the GitHub repository martian56/claude-engineer (2 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 483 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
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
gitlab-helm-deploy
Generate a GitLab CI/CD pipeline and Helm chart that builds the current project with kaniko, pushes to the GitLab Container Registry, and deploys to a Kubernetes namespace via a kubeconfig CI variable. Use when the user asks to set up CI/CD, create a GitLab pipeline, write a Helm chart, containerize and deploy an app…
infra-standards
Infrastructure, container, and CI/CD discipline — IaC, Dockerfiles and compose files, CI pipelines, platform deploy config, env/secrets handling. INVOKE PROACTIVELY when creating or editing any such file (.tf, .bicep, Dockerfile, docker-compose, .github/workflows/, vercel.json) — even when nobody says "infra". Not for…
dockerized-service-release-deployment-workflow
Create a Dockerized-service release contract with clean GitHub Actions builds, main-anchored tags, immutable digest manifests, published-release deployments, production approval, health checks, and exact-digest rollback.
craft-infra
The Craftsman standard for production infrastructure — deployment, env/config, CI/CD, IaC, health/readiness, scaling, platform/edge rate limiting, build/release, rollback. Use WHENEVER work touches infra: deploy, CI gates, env vars, IaC, load failures, platform rate limiting, pooling runtime constraints, or production…
expert-devops
DevOps/infrastructure specialist — CI/CD pipelines, Docker, Kubernetes, cloud config, deploy strategy, monitoring, incident triage, migrations. Use for any task touching build systems, environments, releases, or reliability. Normally invoked by model-router.