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 OKHP3/skillz --skill deployment-strategiesgit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/deployment-strategies)<a href="https://agentmods.dev/skills/okhp3/skillz/deployment-strategies"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/deployment-strategies/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.
<a href="https://agentmods.dev/skills/okhp3/skillz/deployment-strategies"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/deployment-strategies.svg" alt="Reviewed on agentmods" width="80" 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.00098 | $0.01021 |
| Opus 5 | $0.00049 | $0.00511 |
| Sonnet 5 | $0.00020 | $0.00204 |
| Haiku 4.5 | $0.00010 | $0.00102 |
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 6d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment strategies
Every deployment strategy is a way of buying information before you are fully committed. They differ in what they cost and how much they tell you.
The question that decides everything: how quickly can you undo it, and what does undo not cover? A strategy without a tested rollback is not a strategy.
1. Separate deploy from release
The most useful idea here, and the one that unlocks the rest. Deploying is shipping the code; releasing is turning the behaviour on. When they are the same event, every deploy is risky and every rollback is a deploy.
Split them with a flag, and you can ship code continuously, turn a feature on for one account, and turn it off in seconds without a build.
Done when: you can change behaviour without shipping code.
2. Choose the strategy the risk warrants
| Strategy | Buys you | Costs |
|---|---|---|
| Rolling | Simple, no extra capacity | Both versions live at once; slow rollback |
| Blue-green | Instant switch and instant rollback | Double capacity during the switch |
| Canary | Real traffic on a small blast radius | Needs traffic splitting and per-version metrics |
| Feature flag | Per-user control, instant off | Flag debt, and both code paths must work |
| Shadow | Zero risk, real inputs | No user-visible result; needs response comparison |
Most changes need nothing more than rolling. Reserve the expensive strategies for changes that are hard to undo or hard to test, and note that the two-version overlap in rolling and canary is itself a constraint: both versions must tolerate each other's data.
Done when: the strategy matches the cost of being wrong.
3. Make rollback the first thing you test
Not the last. Rehearse it before the deploy that needs it.
- Time it. "We can roll back" means nothing if it takes 40 minutes
- Know what it does not undo: migrations already applied, messages already sent, caches already poisoned, data already written in the new shape. This list is the real risk
- Keep the previous version warm where the strategy allows an instant switch
- Roll back first, diagnose second. During an incident, understanding is not the priority.
See
incident-response
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.
- 6d ago First seen · 96 lines · 98 tokens per session scan A af93c03d9f6b
deployment-strategies is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 1,021 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
vastai-sdk
Vast.ai Python SDK — high-level API for GPU instances, volumes, serverless endpoints, and billing.
pm-aarrr
A post-launch product-growth workflow based on AARRR: acquiring users, activating them, retaining them, earning revenue, and gaining referrals.
pm-docs
A workflow for producing product documents such as PRDs, BRDs, and MRDs. These are structured documents describing what a product needs, its business case, and its market.
pm-position
A guided process for defining a product’s market position, value, audience, competitive difference, business model, pricing, and revenue plan. The instructions are written mainly in Chinese.
pm-retro
A retrospective workflow for reviewing a finished agile iteration, recording what happened, and choosing improvements for the next cycle.
product-marketing-copywriter
A marketing-copy tool that analyzes audience problems and product benefits, then creates promotional headlines and body text. Marketing copy is writing intended to explain and promote a product.