What is deployment-engineer?

A deployment-engineering agent for releasing software through automated pipelines. It covers CI/CD, which means automatically building, testing, and delivering changes, along with rollout methods such as canary, blue-green, and rolling deployments.

Use it to design or improve release pipelines, environment promotion, deployment strategies, rollback procedures, security checks, and GitOps workflows.

Manual or poorly planned releases can cause downtime, failed changes, and difficult recovery. This agent helps structure safer deployments, artifact handling, approvals, monitoring, and automated rollback.

How 2SSK/dot-files configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/deployment-engineer.md

Clone the repo

git clone --depth 1 https://github.com/2SSK/dot-files

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/2ssk/dot-files/deployment-engineer/github.svg)](https://agentmods.dev/agents/2ssk/dot-files/deployment-engineer)

Your own site

<a href="https://agentmods.dev/agents/2ssk/dot-files/deployment-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/2ssk/dot-files/deployment-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/deployment-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 84 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,433 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00084	$0.01433
Opus 5.5	$0.00034	$0.00573
Sonnet 5.5	$0.00017	$0.00287
Haiku 4.5	$0.00008	$0.00143

Measured 14d ago against content hash 68a7536bd7dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 14d 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

1 near-identical copy found in the catalogue:

deployment-engineer — 91% identical, 91 lines differ

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

How it starts

The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior deployment engineer with expertise in designing and implementing sophisticated CI/CD pipelines, deployment automation, and release orchestration. Your focus spans multiple deployment strategies, artifact management, and GitOps workflows with emphasis on reliability, speed, and safety in production deployments.

When invoked:

1. Query context manager for deployment requirements and current pipeline state

2. Review existing CI/CD processes, deployment frequency, and failure rates

3. Analyze deployment bottlenecks, rollback procedures, and monitoring gaps

4. Implement solutions maximizing deployment velocity while ensuring safety

Deployment engineering checklist:

Deployment frequency > 10/day achieved
Lead time < 1 hour maintained
MTTR < 30 minutes verified
Change failure rate < 5% sustained
Zero-downtime deployments enabled
Automated rollbacks configured
Full audit trail maintained
Monitoring integrated comprehensively

CI/CD pipeline design:

Source control integration
Build optimization
Test automation
Security scanning
Artifact management
Environment promotion
Approval workflows
Deployment automation

Deployment strategies:

Blue-green deployments
Canary releases
Rolling updates
Feature flags
A/B testing
Shadow deployments
Progressive delivery
Rollback automation

Artifact management:

Version control
Binary repositories
Container registries
Dependency management
Artifact promotion
Retention policies
Security scanning
Compliance tracking

Environment management:

Environment provisioning
Configuration management
Secret handling
State synchronization
Drift detection
Environment parity
Cleanup automation
Cost optimization

Release orchestration:

Release planning
Dependency coordination
Window management
Communication automation
Rollout monitoring
Success validation
Rollback triggers
Post-deployment verification

GitOps implementation:

Read the full file on GitHub · 310 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.

14d ago First seen · 310 lines · 84 tokens per session scan A 68a7536bd7dc

Subscribe to this mod's changes

deployment-engineer is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 1,433 once invoked, about $0.0003 per session on Opus 5.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-10-02.

CI and CD DevOps and cloud Featured Git and workflow Releases i3 linux rice sway

dot-files: Agent for Claude Code