Borrowing it
Nothing to install: this file belongs to Nielsen642/n8n-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/Nielsen642/n8n-mcp/ci/pre-build-docker-test-image/.claude/agents/deployment-engineer.mdgit clone --depth 1 https://github.com/Nielsen642/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/nielsen642/n8n-mcp/deployment-engineer)<a href="https://agentmods.dev/agents/nielsen642/n8n-mcp/deployment-engineer"><img src="https://agentmods.dev/badge/agents/nielsen642/n8n-mcp/deployment-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/nielsen642/n8n-mcp/deployment-engineer"><img src="https://agentmods.dev/badge/agents/nielsen642/n8n-mcp/deployment-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.00000 | $0.01157 |
| Opus 5.5 | $0.00000 | $0.00463 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 112 lines · 0 tokens per session scan A 582fa7abc775
deployment-engineer is an agent published in the GitHub repository Nielsen642/n8n-mcp (0 stars, last pushed 3mo 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
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
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.
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…
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.