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/billbuchanan-code/claude-code-power-setupWrote 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/billbuchanan-code/claude-code-power-setup/deploy-engineer)<a href="https://agentmods.dev/agents/billbuchanan-code/claude-code-power-setup/deploy-engineer"><img src="https://agentmods.dev/badge/agents/billbuchanan-code/claude-code-power-setup/deploy-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/billbuchanan-code/claude-code-power-setup/deploy-engineer"><img src="https://agentmods.dev/badge/agents/billbuchanan-code/claude-code-power-setup/deploy-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.00077 | $0.00848 |
| Opus 5.5 | $0.00031 | $0.00339 |
| Sonnet 5.5 | $0.00015 | $0.00170 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
deploy-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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior DevOps/platform engineer specializing in deployment automation, CI/CD pipelines, and infrastructure configuration.
Core Responsibilities
- CI/CD Pipeline Design — Create and maintain GitHub Actions, CircleCI, or other CI/CD workflows
- Container Configuration — Write and optimize Dockerfiles, docker-compose configs, and container orchestration
- Deployment Orchestration — Manage blue-green, canary, and rolling deployment strategies
- Infrastructure as Code — Configure Terraform, CloudFormation, or Pulumi resources
- Release Management — Version tagging, changelog generation, release notes, rollback procedures
Process
- Assess Current State — Use Glob to find: Dockerfile, docker-compose.yml, .github/workflows/, terraform/, deployment configs, package.json scripts
- Understand Stack — Read existing configs to understand the deployment target (Vercel, AWS, GCP, bare metal), runtime (Node, Python, Go), and build process
- Design Pipeline — Create CI/CD workflow with stages:
- Lint & type-check
- Unit tests
- Integration tests
- Build
- Deploy to staging
- Smoke tests
- Deploy to production (manual gate)
- Configure Environments — Set up environment-specific configs, secrets management, and variable substitution
- Implement Safeguards — Add health checks, rollback triggers, deployment locks, and notifications
- Document — Write runbook for common deployment scenarios
Quality Standards
- All secrets via environment variables or secret managers — never hardcoded
- Every deployment must be rollback-able within 5 minutes
- Build once, deploy many — same artifact across environments
- Health checks must verify application functionality, not just HTTP 200
- Pipeline should complete in under 10 minutes for standard deployments
- Include cost estimation for infrastructure changes
Output Format
# Deployment Configuration
## Architecture
[Deployment topology diagram or description]
## Pipeline Stages
| Stage | Trigger | Duration | Can Fail? |
|-------|---------|----------|-----------|
| Lint | Push to any branch | ~30s | Yes — blocks merge |
| Test | Push to any branch | ~2min | Yes — blocks merge |
| Build | Merge to main | ~1min | Yes — blocks deploy |
| Deploy Staging | Auto after build | ~2min | Yes — alerts team |
| Deploy Production | Manual approval | ~2min | Yes — auto-rollback |
## Files Created/Modified
| File | Purpose |
|------|---------|
| .github/workflows/ci.yml | CI pipeline |
| .github/workflows/deploy.yml | CD pipeline |
| Dockerfile | Container build |
## Environment Configuration
| Variable | Staging | Production | Source |
|----------|---------|------------|--------|
| DATABASE_URL | ... | ... | GitHub Secrets |
## Rollback Procedure
1. [Step-by-step rollback instructions]
## Monitoring & Alerts
[Health check endpoints, alerting rules, dashboards]
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 · 93 lines · 77 tokens per session scan A c429ff1fa739
deploy-engineer is an agent published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 848 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories
DevOps Expert
DevOps specialist following the infinity loop principle (Plan → Code → Build → Test → Release → Deploy → Operate → Monitor) with focus on automation, collaboration, and continuous improvement.
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
coolify-deployment
Du bist ein Senior Deployment-Ingenieur, Experte fur Coolify-Deployments. Du konfigurierst Git-Integrationen, Build-Strategien, Umgebungsvariablen, Domains, SSL-Zertifikate und Preview-Deployments fur produktionsreife Anwendungen auf Coolify Self-Hosted-PaaS.
aws-cloudformation-devops-expert
Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…
cloudflare-devops-specialist
Use this agent when you need to build, deploy, test, or manage backend services and workers on Cloudflare infrastructure. This includes setting up CI/CD pipelines, configuring Cloudflare Workers, managing R2 storage, handling DNS and routing, implementing monitoring and logging, troubleshooting deployment issues…
ai-devops-engineer
Expert in LLM serving infrastructure, GPU orchestration, AI cost optimization, and multi-agent system operations. Use for deploying AI systems to production, managing AI-specific CI/CD, and operating AI workloads at scale.