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 skills add glincker/claude-code-marketplace --skill deployment-managergit clone --depth 1 https://github.com/glincker/claude-code-marketplaceWrote 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/skills/glincker/claude-code-marketplace/deployment-manager)<a href="https://agentmods.dev/skills/glincker/claude-code-marketplace/deployment-manager"><img src="https://agentmods.dev/badge/skills/glincker/claude-code-marketplace/deployment-manager.svg" alt="Measured on agentmods" 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.00019 | $0.01943 |
| Opus 5 | $0.00010 | $0.00971 |
| Sonnet 5 | $0.00004 | $0.00389 |
| Haiku 4.5 | $0.00002 | $0.00194 |
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 7d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Manager
Advanced deployment orchestration agent for automated, safe, and reliable application deployments. Supports multiple deployment strategies, automatic rollback, and production-ready workflows.
Agent Expertise
- Zero-downtime deployments
- Blue-green deployment strategy
- Canary releases with progressive rollout
- Automated rollback on failure
- Multi-environment deployment (dev, staging, prod)
- Database migration coordination
- Health checks and validation
- Deployment pipeline orchestration
Key Capabilities
- Deployment Strategies: Blue-green, canary, rolling updates, recreate
- Automated Rollback: Automatic rollback on health check failures
- Database Migrations: Safe schema changes with rollback support
- Health Monitoring: Pre and post-deployment validation
- Traffic Management: Progressive traffic shifting for canary deployments
- Multi-Cloud Support: AWS, GCP, Azure, and on-premise
Workflow
When activated, this agent will:
- Analyze application architecture and deployment requirements
- Select appropriate deployment strategy
- Run pre-deployment health checks
- Execute deployment with safety measures
- Monitor application health during rollout
- Automatically rollback if issues detected
- Notify stakeholders of deployment status
Quick Commands
# Deploy to production
"Deploy the application to production using blue-green strategy"
# Canary release
"Deploy new version to 10% of users, then gradually increase"
# Deploy with migration
"Deploy application and run database migrations safely"
# Rollback
"Rollback the last production deployment"
# Setup deployment pipeline
"Create automated deployment pipeline for this application"
# Multi-environment deploy
"Deploy to staging, wait for approval, then deploy to production"
Deployment Strategies
Blue-Green Deployment
Zero-downtime deployment:
- Deploy new version (Green) alongside current (Blue)
- Run health checks on Green environment
- Switch traffic from Blue to Green
- Keep Blue as instant rollback option
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 325 lines · 19 tokens per session scan A d36e19b21c7e
deployment-manager is a skill published in the GitHub repository glincker/claude-code-marketplace (36 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,943 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 skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
cicd-expert
Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation. Use when the user mentions CI/CD, GitHub Actions, Jenkins, GitLab CI, deployment, or automation, or when the task involves CI/CD Fundamentals, Pipeline Design, Workflow Basics, or Docker Build and Push.
cicd-agent
CI/CD pipeline design and review — GitHub Actions, pipeline best practices, secrets management, deployment strategies, and release automation.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
Canary Deployment Testing
Canary deployment validation testing including traffic splitting, metric comparison, automatic rollback triggers, and health score calculation.