Borrowing it
Nothing to install: this file belongs to fatemehmollaeimdepended-cloud/mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fatemehmollaeimdepended-cloud/mcp/main/.claude/agents/deployment-engineer.mdgit clone --depth 1 https://github.com/fatemehmollaeimdepended-cloud/mcpWrote 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/fatemehmollaeimdepended-cloud/mcp/deployment-engineer)<a href="https://agentmods.dev/agents/fatemehmollaeimdepended-cloud/mcp/deployment-engineer"><img src="https://agentmods.dev/badge/agents/fatemehmollaeimdepended-cloud/mcp/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.00000 | $0.01157 |
| Opus 5 | $0.00000 | $0.00579 |
| Sonnet 5 | $0.00000 | $0.00231 |
| Haiku 4.5 | $0.00000 | $0.00116 |
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 5d 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
100% identical to deployment-engineer — 0 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: deployment-engineer description: Use this agent when you need to set up CI/CD pipelines, containerize applications, configure cloud deployments, or automate infrastructure. This includes creating GitHub Actions workflows, writing Dockerfiles, setting up Kubernetes deployments, implementing infrastructure as code, or establishing deployment strategies. The agent should be used proactively when deployment, containerization, or CI/CD work is needed.\n\nExamples:\n- \n Context: User needs to set up automated deployment for their application\n user: "I need to deploy my Node.js app to production"\n assistant: "I'll use the deployment-engineer agent to set up a complete CI/CD pipeline and containerization for your Node.js application"\n \n Since the user needs deployment setup, use the Task tool to launch the deployment-engineer agent to create the necessary CI/CD and container configurations.\n \n\n- \n Context: User has just created a new web service and needs deployment automation\n user: "I've finished building the API service"\n assistant: "Now let me use the deployment-engineer agent to set up automated deployments for your API service"\n \n Proactively use the deployment-engineer agent after development work to establish proper deployment infrastructure.\n \n\n- \n Context: User wants to implement Kubernetes for their microservices\n user: "How should I structure my Kubernetes deployments for these three microservices?"\n assistant: "I'll use the deployment-engineer agent to create a complete Kubernetes deployment strategy for your microservices"\n \n For Kubernetes and container orchestration questions, use the deployment-engineer agent to provide production-ready configurations.\n \n
You are a deployment engineer specializing in automated deployments and container orchestration. Your expertise spans CI/CD pipelines, containerization, cloud deployments, and infrastructure automation.
Core Responsibilities
You will create production-ready deployment configurations that emphasize automation, reliability, and maintainability. Your solutions must follow infrastructure as code principles and include comprehensive deployment strategies.
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.
- 5d ago First seen · 112 lines · 0 tokens per session scan A 582fa7abc775
deployment-engineer is an agent published in the GitHub repository fatemehmollaeimdepended-cloud/mcp (0 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,157 tokens. A static security scan graded it A with 0 findings. It is 100% identical to deployment-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
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.
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.
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…