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/caiaffa/claude-code-ultimate-engineering-system/infra-devopsnpx skills add caiaffa/claude-code-ultimate-engineering-system --skill infra-devopsgit clone --depth 1 https://github.com/caiaffa/claude-code-ultimate-engineering-systemWhat 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.00026 | $0.00500 |
| Opus 5 | $0.00013 | $0.00250 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
infra-devops 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 2d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Raise the quality of delivery systems and runtime environments so software is not only built, but reliably shipped and operated.
When to use
- Reviewing CI/CD pipelines.
- Improving deployment safety.
- Validating secrets/config handling.
- Checking runtime health and autoscaling.
- Evaluating IaC drift or quality.
Handoff
- Receives from: backend-platform-engineer (deployment needs) or release-commander (rollout planning).
- Hands off to: kubernetes-operability (if K8s), aws-production-systems (if AWS), release-commander (deploy readiness).
CI/CD quality checklist
- Build reproducibility — same commit always produces same artifact?
- Test gates — what tests must pass before deploy? any flaky tests bypassed?
- Security scan — dependency vulnerabilities checked? secrets scanning?
- Artifact immutability — build once, deploy everywhere (no rebuild per env)?
- Deploy safety — canary/rolling? automatic rollback on failure?
- Pipeline speed — < 10 min for PR checks? < 20 min for full deploy?
Config and secret hygiene
| Good | Bad |
|---|---|
| Secrets in Vault/SSM/Secrets Manager | Secrets in env files in repo |
| Config externalized, environment-specific | Config hardcoded, differs by branch |
| Secret rotation tested and automated | Secrets rotated manually once a year |
| Config validated at startup | App starts with missing config, fails later |
Red flags
- CI passes but deploy is a manual script.
- "Works on staging" but staging is months behind production.
- Health check returns 200 always, regardless of dependency state.
- Rollback requires manual database changes.
- IaC exists but actual infrastructure has drifted.
- Secret rotation would require downtime.
Output format
- Pipeline assessment (build, test, deploy quality)
- Config/secret hygiene (risks found)
- Runtime health (probes, scaling, resource config)
- Key risks (prioritized by blast radius)
- Recommendations (with implementation order)
- Rollback practicality (can we actually roll back?)
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.
- 2d ago First seen · 51 lines · 26 tokens per session scan A 009e4ba00034
infra-devops is a skill published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 500 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-30.
Other skills, from other repositories
google-agents-cli-deploy
This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud Run, or GKE deployment targets, or binding an agent to an Agent Gateway. Covers deployment workflows, service accounts…
deploy-status
Check civitai PROD deployment status across the live Tekton -> Flux -> Flagger chain on the DataPacket cluster (kubectl, read-only). Tekton/Flagger cluster state is the primary truth; the GitHub Deployments API is kept as a public cross-check. Use to see where a deploy is in the chain, watch it to completion, or debug…
aws-deployment
Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact. Covers CodePipeline V2 (triggers, variables, execution modes, cross-account), buildspec.yml (caching, VPC, Docker), CodeDeploy strategies (blue/green, canary, linear), CodeArtifact (private package registries…
use-vercel-action
Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI. Use when the user asks to deploy to Vercel from GitHub Actions, add Vercel preview deploys, post a Vercel preview URL on a PR, configure prebuilt Vercel deployments, set up alias domains for previews, create a GitHub…
cd-pipeline-generator
Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure). Use when setting up continuous deployment pipelines, creating deployment automation, or configuring multi-environment deployment strategies. Includes templates for…
devops-excellence
DevOps and CI/CD expert. Use when setting up pipelines, containerizing applications, deploying to Kubernetes, or implementing release strategies. Covers GitHub Actions, Docker, K8s, Terraform, and GitOps.