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 skills/cyperx84/claude-code-plugin-examples/deployment-strategiesnpx skills add cyperx84/claude-code-plugin-examples --skill deployment-strategiesgit clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examplesWrote 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/cyperx84/claude-code-plugin-examples/deployment-strategies)<a href="https://agentmods.dev/skills/cyperx84/claude-code-plugin-examples/deployment-strategies"><img src="https://agentmods.dev/badge/skills/cyperx84/claude-code-plugin-examples/deployment-strategies.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 | $0.00026 | $0.02782 |
| Opus 5 | $0.00013 | $0.01391 |
| Sonnet 5 | $0.00005 | $0.00556 |
| Haiku 4.5 | $0.00003 | $0.00278 |
Grade A, and why
Deployment Strategies 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.
How it starts
The opening of the file, as written. The whole thing — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Strategies
Purpose
Master production deployment strategies:
- Zero-downtime deployments
- Risk mitigation
- Rollback procedures
- Progressive delivery
- Infrastructure patterns
When to Use
Invoke this skill when:
- Planning production deployments
- Designing deployment pipelines
- Troubleshooting failed deploys
- Implementing new deployment strategy
- Reducing deployment risk
Deployment Strategies
1. Blue-Green Deployment
Concept: Two identical environments (Blue=current, Green=new)
┌─────────────┐
│ Load │
│ Balancer │
└──────┬──────┘
│
├─────────────┐
│ │
┌────▼───┐ ┌───▼────┐
│ Blue │ │ Green │
│ (v1.0) │ │ (v2.0) │
│ LIVE │ │ IDLE │
└────────┘ └────────┘
After testing Green:
Switch traffic → Green becomes LIVE
If issues:
Switch back → Instant rollback
Implementation:
// Example using AWS ELB
async function blueGreenDeploy(version: string): Promise<void> {
// 1. Deploy to green environment
await deployToEnvironment('green', version);
// 2. Run smoke tests on green
const testsPass = await runSmokeTests('green');
if (!testsPass) {
throw new Error('Green environment failed tests');
}
// 3. Gradually shift traffic
await shiftTraffic('blue', 'green', {
steps: [10, 25, 50, 100],
intervalMinutes: 5,
});
// 4. Monitor for errors
const errors = await monitorErrors('green', { duration: '10m' });
if (errors > THRESHOLD) {
await rollback('blue');
throw new Error('Rollback triggered due to errors');
}
// 5. Decommission blue
await decommission('blue');
}
Pros: ✅ Instant rollback, ✅ Zero downtime, ✅ Full testing before switch Cons: ❌ 2x infrastructure cost, ❌ Database migrations tricky
2. Canary Deployment
Concept: Gradually roll out to small percentage of users
Phase 1: 5% traffic → v2.0
95% traffic → v1.0
Phase 2: 25% traffic → v2.0
75% traffic → v1.0
Phase 3: 50% traffic → v2.0
50% traffic → v1.0
Phase 4: 100% traffic → v2.0
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.
- 4d ago First seen · 467 lines · 26 tokens per session scan A 168154f1448d
Deployment Strategies is a skill published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 10mo ago), licensed MIT. It adds 26 tokens to every session and 2,782 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-31.
Other skills, from other repositories
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
atmos-auth
Authentication and identity management: providers (SSO/SAML/OIDC/GCP/Atmos Pro), identities, keyring, identity chaining, login/exec/shell/console, and github/sts for private GitHub access.