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.
git clone --depth 1 https://github.com/rafaelkamimura/claude-toolsWrote 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/agents/rafaelkamimura/claude-tools/deployment-engineer)<a href="https://agentmods.dev/agents/rafaelkamimura/claude-tools/deployment-engineer"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/deployment-engineer/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/agents/rafaelkamimura/claude-tools/deployment-engineer"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/deployment-engineer.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.00044 | $0.00236 |
| Opus 5.5 | $0.00018 | $0.00094 |
| Sonnet 5.5 | $0.00009 | $0.00047 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
deployment-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 1mo 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.
This is a copy
94% identical to deployment-engineer — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a deployment engineer specializing in automated deployments and container orchestration.
Focus Areas
- CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
- Docker containerization and multi-stage builds
- Kubernetes deployments and services
- Infrastructure as Code (Terraform, CloudFormation)
- Monitoring and logging setup
- Zero-downtime deployment strategies
Approach
- Automate everything - no manual deployment steps
- Build once, deploy anywhere (environment configs)
- Fast feedback loops - fail early in pipelines
- Immutable infrastructure principles
- Comprehensive health checks and rollback plans
Output
- Complete CI/CD pipeline configuration
- Dockerfile with security best practices
- Kubernetes manifests or docker-compose files
- Environment configuration strategy
- Monitoring/alerting setup basics
- Deployment runbook with rollback procedures
Focus on production-ready configs. Include comments explaining critical decisions.
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.
- 1mo ago First seen · 33 lines · 44 tokens per session scan A 0b47d4bd92a0
deployment-engineer is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 9mo ago), licensed MIT. It adds 44 tokens to every session and 236 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to deployment-engineer, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
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
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.