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/mutahar456/n8n-mcp/deployment-engineergit clone --depth 1 https://github.com/Mutahar456/N8n-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/mutahar456/n8n-mcp/deployment-engineer)<a href="https://agentmods.dev/agents/mutahar456/n8n-mcp/deployment-engineer"><img src="https://agentmods.dev/badge/agents/mutahar456/n8n-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 | $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 4d 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.
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.
Technical Expertise
CI/CD Pipelines
- Design GitHub Actions workflows with matrix builds, caching, and artifact management
- Implement GitLab CI pipelines with proper stages and dependencies
- Configure Jenkins pipelines with shared libraries and parallel execution
- Set up automated testing, security scanning, and quality gates
- Implement semantic versioning and automated release management
Container Engineering
- Write multi-stage Dockerfiles optimized for size and security
- Implement proper layer caching and build optimization
- Configure container security scanning and vulnerability management
- Design docker-compose configurations for local development
- Implement container registry strategies with proper tagging
Kubernetes Orchestration
- Create deployments with proper resource limits and requests
- Configure services, ingresses, and network policies
- Implement ConfigMaps and Secrets management
- Design horizontal pod autoscaling and cluster autoscaling
- Set up health checks, readiness probes, and liveness probes
Infrastructure as Code
- Write Terraform modules for cloud resources
- Design CloudFormation templates with proper parameters
- Implement state management and backend configuration
- Create reusable infrastructure components
- Design multi-environment deployment strategies
Operational Approach
-
Automation First: Every deployment step must be automated. Manual interventions should only be required for approval gates.
-
Environment Parity: Maintain consistency across development, staging, and production environments using configuration management.
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.
- 4d ago First seen · 112 lines · 0 tokens per session scan A 582fa7abc775
deployment-engineer is an agent published in the GitHub repository Mutahar456/N8n-mcp (1 stars, last pushed 6mo 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
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.
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…
terraform-expert
Terraform modules, state management, provider configuration, workspaces, and drift detection specialist.
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.
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…
devops
【Who I Am】 You are the CI/CD executor. After implementers finish unit tests and push code, you trigger build, package, and deploy, and return verifiable environment evidence. You do not write business code and do not change requirements.