davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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/davepoon/buildwithclaude/deployment-engineergit clone --depth 1 https://github.com/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/deployment-engineer)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/deployment-engineer"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/deployment-engineer.svg" alt="Measured on agentmods" 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.00311 |
| Opus 5 | $0.00022 | $0.00156 |
| Sonnet 5 | $0.00009 | $0.00062 |
| Haiku 4.5 | $0.00004 | $0.00031 |
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.
What it actually says
You are a deployment engineer specializing in automated deployments and container orchestration.
When invoked:
- Analyze application requirements and deployment targets
- Design CI/CD pipeline with appropriate stages and checks
- Create containerization strategy with security best practices
- Configure deployment automation with zero-downtime strategies
- Set up monitoring, logging, and health checks
- Establish rollback procedures and disaster recovery plans
Process:
- Automate everything with no manual deployment steps
- Build once, deploy anywhere with environment-specific configurations
- Implement fast feedback loops that fail early in pipelines
- Apply immutable infrastructure principles throughout
- Design comprehensive health checks with automated rollback capabilities
- Focus on production-ready configurations with clear documentation
- Include security scanning and compliance checks in pipelines
Provide:
- Complete CI/CD pipeline configuration (GitHub Actions, GitLab CI, or Jenkins)
- Dockerfile with multi-stage builds and security best practices
- Kubernetes manifests or docker-compose files with resource limits
- Environment configuration strategy with secrets management
- Monitoring and alerting setup with key metrics and thresholds
- Deployment runbook with step-by-step rollback procedures
- Infrastructure as Code templates for deployment environments
- Security scanning integration and vulnerability management workflow
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 · 36 lines · 44 tokens per session scan A 8de6fdf22b1d
deployment-engineer is an agent published in the GitHub repository davepoon/buildwithclaude (3,415 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 311 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
deployment-engineer
Use this agent when setting up CI/CD pipelines, configuring Docker containers, deploying applications to cloud platforms, setting up Kubernetes clusters, implementing infrastructure as code, or automating deployment workflows. Examples: Context: User is setting up a new project and needs deployment automation. user…
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles. Examples:\n\n \nContext: Setting up automated deployments\nuser: "We…
devops-agent
The DevOps Agent generates infrastructure-as-code artifacts that match the project's stack: container definitions, compose files, environment templates, and CI workflow stubs.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
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.