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 launch-plangit 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/launch-plan)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/launch-plan"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/launch-plan/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/launch-plan"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/launch-plan.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.00030 | $0.00870 |
| Opus 5 | $0.00015 | $0.00435 |
| Sonnet 5 | $0.00006 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
launch-plan 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 10d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Plan
Overview
A launch plan coordinates every function involved in shipping — engineering, design, marketing, support, sales, legal — into a single timeline with clear owners and checkpoints. This skill guides you from pre-launch preparation through post-launch monitoring.
When to Use
- You're shipping a major feature or new product
- Multiple teams need to coordinate their launch activities
- You want to avoid last-minute scrambling on launch day
- Don't use for: simple bug fixes or minor improvements (use a ticket checklist instead)
Instructions
1. Define Launch Tier
Not every feature needs a full launch. Classify:
- Tier 1 (Major): New product, major feature, public beta. Full marketing campaign
- Tier 2 (Standard): Significant feature update. Blog post, in-app announcement
- Tier 3 (Minor): Small improvement. Release notes mention only
- Tier 4 (Maintenance): Bug fix, performance, tech debt. No announcement
2. Pre-Launch Phase (T-4 weeks to T-1 week)
For each area:
- Engineering: Code complete, code review, QA testing, bug fixing
- Design: Final visual QA, edge case screens
- Docs: Help articles, release notes, API docs
- Marketing: Landing page, blog post, social media, email
- Support: FAQ, training docs, agent scripts
- Sales: Pitch deck, pricing updates, enablement materials
- Legal: Terms of service, privacy policy, compliance review
3. Launch Prep Phase (T-1 week to D-Day)
- QA sign-off: All P0 and P1 bugs fixed
- Staging verification: End-to-end test passes on staging
- Performance check: Load testing, response time targets met
- Rollback plan: Tested and documented
- Go/no-go meeting: Final decision to launch
- Communication ready: All announcements prepared and scheduled
4. Launch Day
- Monitor: Dashboards for errors, latency, usage, and support tickets
- Communicate: Release notes published, in-app banner live, announcements sent
- Support: Support team briefed and ready for increased volume
- Rollback criteria defined: "If error rate > 1% for 5 minutes, roll back"
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.
- 10d ago First seen · 100 lines · 30 tokens per session scan A 829d77138ad6
launch-plan is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 870 once invoked, about $0.0002 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…