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 uthumany/uthy-legacy-os --skill rollout-strategygit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/rollout-strategy)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/rollout-strategy"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/rollout-strategy/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/uthumany/uthy-legacy-os/rollout-strategy"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/rollout-strategy.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.00028 | $0.00728 |
| Opus 5 | $0.00014 | $0.00364 |
| Sonnet 5 | $0.00006 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
rollout-strategy 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 11d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rollout Strategy
Overview
Rollout strategy is about managing risk during deployment. Instead of flipping a switch for everyone, you gradually increase exposure, monitoring for problems at each step, with a clear rollback plan if things go wrong. This skill covers feature flags, canary releases, and progressive delivery.
When to Use
- Shipping a feature with significant user impact
- Making infrastructure or architectural changes
- Introducing breaking API changes
- Releasing to users who depend on reliability
- Don't use for: trivial UI changes, content updates, or features behind an opt-in beta already
Instructions
1. Define the Rollout Phases
Phase 0: Internal — Dogfood with your own team
- Goals: Catch obvious bugs, test basic functionality
- Duration: 1-3 days
- Success criteria: No P0 bugs, team can use the feature
Phase 1: Alpha — 5-10% of users, internal only
- Goals: Validate performance, catch edge cases
- Duration: 3-7 days
- Success criteria: Error rate < 0.1%, latency within SLA
Phase 2: Beta — 25-50% of users
- Goals: Broader validation, gather feedback
- Duration: 5-14 days
- Success criteria: Error rate stable, support volume normal, feedback positive
Phase 3: GA — 100% of users
- Goals: Complete availability
- Success criteria: All metrics stable, launch criteria met
2. Choose the Mechanism
- Feature flags: Code-deployed but flag-off. Toggle based on user ID, account ID, or region
- Canary release: New version serves a subset of traffic. Gradually increase
- Shadow mode: New system runs in parallel, results compared but not served to users
- Blue/green: Two identical environments. Switch traffic when ready
3. Define Monitoring Gates
At each phase, monitor:
- Error rate: Spikes above baseline?
- Latency: P95 within SLA?
- User impact: Crash rate, support tickets?
- Business metrics: Revenue, engagement, retention changes?
- Hard rollback trigger: "If [metric] exceeds [threshold] for [duration], auto-rollback"
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.
- 11d ago First seen · 89 lines · 28 tokens per session scan A a28ce90cdb1e
rollout-strategy is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 728 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…