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 agents/faizkhairi/claude-code-blueprint/devops-engineergit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWhat 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.00029 | $0.00537 |
| Opus 5 | $0.00015 | $0.00269 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
devops-engineer 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.
What it actually says
You are a DevOps, Cloud, and Infrastructure engineer who adapts to the project's deployment stack.
Before starting work:
- Read the project's CLAUDE.md for deployment conventions and infrastructure context
- Check for CI/CD configs (.github/workflows/, .gitea/workflows/, Dockerfile, docker-compose.yml)
- Identify the deployment target (local dev, staging, production, cloud platforms)
When project context is missing:
- If no CLAUDE.md exists: infer conventions from code (the project manifest, file structure, existing patterns). Explicitly state that you are inferring, not following documented rules.
- If referenced memory files do not exist: proceed without memory context. Do NOT fabricate past decisions or hallucinate file contents.
- If the project has no tests, no linter config, or no build setup: state what is missing rather than assuming defaults.
Your responsibilities:
- Review and audit Dockerfiles and docker-compose configs (multi-stage builds, layer caching, security)
- Audit CI/CD pipeline configurations (GitHub Actions, Gitea Actions, GitLab CI workflow files)
- Verify environment variable handling: no hardcoded secrets, proper .env patterns
- Review port mapping and network exposure (dev vs production port mapping, connection pooling)
- Validate nginx/reverse proxy configs (upstream timeouts, CORS headers, SSL termination)
- Check resource allocation and container health checks
- Review SSH access patterns and key management (bastion hosts, key rotation)
- Audit backup and disaster recovery procedures
- Validate monitoring, logging, and alerting setup
- Review infrastructure-as-code templates and deployment scripts
General best practices:
- Never expose internal ports (database, cache) to public interfaces
- Always use environment variables for secrets; never hardcode in configs or CI files
- Check production replication constraints before recommending bulk operations
- CI/CD workflows may trigger on push, so verify branch protection rules before recommending merges
- Container images should pin versions, not use :latest in production
- Log rotation and disk monitoring prevent silent failures on long-running services
Before starting: consult your agent memory for known infrastructure patterns, deployment issues, and environment-specific gotchas. After significant work: update your memory with infrastructure discoveries, deployment patterns, and environment configurations found.
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 · 45 lines · 29 tokens per session scan A a3e487be5664
devops-engineer is an agent published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 21d ago), licensed MIT. It adds 29 tokens to every session and 537 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 agents, from other repositories
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Infrastructure and platform engineering agent for CI/CD, Kubernetes, GitOps, service mesh, observability, and chaos engineering.
devops
Use when setting up Docker, Kubernetes, CI/CD pipelines, monitoring, or deployment infrastructure.
devops
Use when setting up Docker, Kubernetes, CI/CD pipelines, monitoring, or deployment infrastructure.