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/yonatangross/orchestkit/deployment-managergit clone --depth 1 https://github.com/yonatangross/orchestkitWhat 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.00024 | $0.02320 |
| Opus 5 | $0.00012 | $0.01160 |
| Sonnet 5 | $0.00005 | $0.00464 |
| Haiku 4.5 | $0.00002 | $0.00232 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 278 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 toolsmcp__github-mcp__*- GitHub releases and deployments
Concrete Objectives
- Plan and execute zero-downtime deployments
- Configure blue-green and canary release strategies
- Implement and manage feature flags
- Create rollback procedures and runbooks
- Monitor deployments and respond to incidents
- 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)
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.
- 2d ago First seen · 278 lines · 24 tokens per session scan A cf75bb283e2c
deployment-manager is an agent published in the GitHub repository yonatangross/orchestkit (224 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 2,320 once invoked, about $0.0001 per session on Opus 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.
Other agents, from other repositories
blue-green-deployment-master
Zero-downtime deployment and rollback specialist.
huyen-agents
Updated 2025: This is a summary of Chip Huyen's blog and book chapter on agents, with some added context to provide a comprehensive overview of their design, capabilities, and practical applications.
lg-react-system-prompt
How the ported LangGraph tool-loop agent composes conduct, workspace, named-service, conversation-recovery, optional turn-summary, and administrator instruction blocks each turn.
devops-agent
PROACTIVELY handles deployment, CI/CD, infrastructure, build systems, and production setup when users need deployment, want hosting, ask about infrastructure, or need build optimization. Use for any DevOps and deployment needs.
quality-agent
PROACTIVELY reviews code quality, validates accessibility, checks security, runs tests, and assesses compliance when users need code review, want quality assessment, ask for testing, or need validation. Use for any quality assurance needs.
readiness-gate
Determines if project phase can advance based on overall completeness.