deployment-engineer

Deployment automation for building, testing, packaging, and releasing software. It covers CI/CD pipelines, where automated checks and deployments run, along with Docker containers and Kubernetes.

In plain words
What is it for?
Writing GitHub Actions, GitLab CI, or Jenkins workflows; creating Dockerfiles; preparing Kubernetes or Docker Compose configurations; and planning health checks, monitoring, and rollback procedures.
Why use it?
It reduces manual release work and makes deployments repeatable, observable, and easier to roll back when something fails.

Agent

Install

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.

agentmods
npx agentmods add agents/rafaelkamimura/claude-tools/deployment-engineer
Clone the repo
git clone --depth 1 https://github.com/rafaelkamimura/claude-tools
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 236 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00236
Opus 5 $0.00022 $0.00118
Sonnet 5 $0.00009 $0.00047
Haiku 4.5 $0.00004 $0.00024

Measured 2d ago against content hash 0b47d4bd92a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

Origin

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.

agents/deployment-engineer.md · 33 lines

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

  1. Automate everything - no manual deployment steps
  2. Build once, deploy anywhere (environment configs)
  3. Fast feedback loops - fail early in pipelines
  4. Immutable infrastructure principles
  5. 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.

Changes

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.

  1. 2d ago First seen · 33 lines · 44 tokens per session scan A 0b47d4bd92a0

Subscribe to this mod's changes

deployment-engineer is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 7mo ago), licensed MIT. It adds 44 tokens to every session and 236 once invoked, about $0.0002 per session on Opus 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.