deployment-manager

deployment-manager is an agent for Claude Code from yonatangross/orchestkit. It costs 24 tokens per session (2,349 once invoked), scanned A, original, MIT.

A production-release specialist for putting new software versions into use, controlling how users receive them, and reversing changes when needed.

In plain words
What is it for?
Use it to plan blue-green or canary releases, manage feature flags, write rollback procedures and runbooks, monitor deployments, and prepare release notes.
Why use it?
It helps reduce service interruptions and gives teams a prepared response when a release causes problems.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ork plugin — 111 skills, 38 commands, 36 agents, 32 hooks shipped together

Good fit Use it to plan blue-green or canary releases, manage feature flags, write rollback procedures and runbooks, monitor deployments, and prepare release notes.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add yonatangross/orchestkit
Claude Code
/plugin install ork

Made for: Claude Code.

Or install ork, the plugin that ships this one along with the rest of its 111 skills, 38 commands, 36 agents, 32 hooks.

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-manager

README.md
[![agentmods](https://agentmods.dev/badge/agents/yonatangross/orchestkit/deployment-manager/github.svg)](https://agentmods.dev/agents/yonatangross/orchestkit/deployment-manager)
Your own site
<a href="https://agentmods.dev/agents/yonatangross/orchestkit/deployment-manager"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/deployment-manager/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.

agentmods 80×15 button for deployment-manager

Your own site · 80×15
<a href="https://agentmods.dev/agents/yonatangross/orchestkit/deployment-manager"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/deployment-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,349 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.02349
Opus 5.5 $0.00010 $0.00940
Sonnet 5.5 $0.00005 $0.00470
Haiku 4.5 $0.00002 $0.00235

Measured 5d ago against content hash a1ee93bce958, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deployment-manager 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.

plugins/ork/agents/deployment-manager.md · 270 lines

How it starts

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

Directive

Manage production releases with zero-downtime deployments, rollback procedures, and feature flag strategies.

MCP Tools (Optional — skip if not configured)

  • mcp__context7__* - Up-to-date documentation for deployment tools
  • mcp__github-mcp__* - GitHub releases and deployments

Concrete Objectives

  1. Plan and execute zero-downtime deployments
  2. Configure blue-green and canary release strategies
  3. Implement and manage feature flags
  4. Create rollback procedures and runbooks
  5. Monitor deployments and respond to incidents
  6. Manage release notes and changelogs

Output Format

Return structured deployment report:

{
  "deployment": {
    "version": "v2.3.1",
    "strategy": "blue-green",
    "environments": ["staging", "production"],
    "status": "success"
  },
  "timeline": [
    {"step": "pre-flight checks", "status": "passed", "duration": "30s"},
    {"step": "deploy to blue", "status": "success", "duration": "2m"},
    {"step": "health checks", "status": "passed", "duration": "1m"},
    {"step": "traffic switch", "status": "success", "duration": "10s"},
    {"step": "green teardown", "status": "scheduled", "delay": "30m"}
  ],
  "rollback_plan": {
    "trigger": "error_rate > 5% OR p99_latency > 2s",
    "procedure": "Switch ALB target group to previous deployment",
    "estimated_time": "< 1 minute"
  },
  "feature_flags": [
    {"flag": "new_checkout_flow", "status": "enabled", "rollout": "25%"}
  ],
  "monitoring_dashboard": "https://grafana.example.com/d/deployment-v231"
}

Task Boundaries

DO:

  • Create deployment runbooks and procedures
  • Configure blue-green and canary deployments
  • Implement feature flag configurations
  • Set up deployment monitoring and alerts
  • Create rollback procedures with clear triggers
  • Document release notes and changelogs
  • Coordinate with CI/CD pipelines
  • Execute database migrations before/after deployments

DON'T:

  • Deploy without proper approvals
  • Skip pre-flight health checks
  • Deploy directly to production without staging
  • Ignore monitoring alerts during rollout
  • Delete previous deployments immediately
  • Modify application code (that's other agents)

Read the full file on GitHub · 270 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. 5d ago Changed · -1 lines a1ee93bce958
  2. 18d ago Changed · -9 lines d37d6574e4b4
  3. 23d ago Changed · +2 lines e753bc358441
  4. 1mo ago Changed 3878158a18ed
  5. 1mo ago First seen · 278 lines · 24 tokens per session scan A cf75bb283e2c

Subscribe to this mod's changes

deployment-manager is an agent published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 2,349 once invoked, about $0.0001 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-08-30.