deployment-engineer

deployment-engineer is an agent for Claude Code from czlonkowski/n8n-mcp. It costs 0 tokens per session (1,157 once invoked), scanned A, original, MIT.

A deployment-engineering agent for releasing software and managing its infrastructure. It works with CI/CD, automated pipelines that build and test code, containers, cloud deployments, and infrastructure configuration.

In plain words
What is it for?
It creates GitHub Actions, GitLab CI, or Jenkins pipelines; writes Dockerfiles and compose files; configures Kubernetes or cloud deployments; and sets up infrastructure as code.
Why use it?
It helps turn a working application into a repeatable, automated release process. It also brings testing, security checks, and deployment settings together in one workflow.

Agent for Claude Code

About the project

n8n-MCP is a Model Context Protocol server that gives AI assistants structured knowledge of n8n's workflow-automation nodes, including their properties, operations, documentation, and examples. It helps developers use AI assistants to create and work with n8n workflows. The catalogue contains skills, agents, and instructions for using it.

czlonkowski/n8n-mcp · 22,825 stars · on GitHub

Install

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.

agentmods
npx agentmods add agents/czlonkowski/n8n-mcp/deployment-engineer
Clone the repo
git clone --depth 1 https://github.com/czlonkowski/n8n-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for deployment-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/czlonkowski/n8n-mcp/deployment-engineer.svg)](https://agentmods.dev/agents/czlonkowski/n8n-mcp/deployment-engineer)
Your own site
<a href="https://agentmods.dev/agents/czlonkowski/n8n-mcp/deployment-engineer"><img src="https://agentmods.dev/badge/agents/czlonkowski/n8n-mcp/deployment-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,157 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 582fa7abc775, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

.claude/agents/deployment-engineer.md · 112 lines

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

  1. Automation First: Every deployment step must be automated. Manual interventions should only be required for approval gates.

  2. Environment Parity: Maintain consistency across development, staging, and production environments using configuration management.

Read the full file on GitHub · 112 lines

Changes

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.

  1. 4d ago First seen · 112 lines · 0 tokens per session scan A 582fa7abc775

Subscribe to this mod's changes

deployment-engineer is an agent published in the GitHub repository czlonkowski/n8n-mcp (22,825 stars, last pushed today), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.