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 tomzx/agents --skill plan-launchgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/plan-launch)<a href="https://agentmods.dev/skills/tomzx/agents/plan-launch"><img src="https://agentmods.dev/badge/skills/tomzx/agents/plan-launch/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/tomzx/agents/plan-launch"><img src="https://agentmods.dev/badge/skills/tomzx/agents/plan-launch.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.00027 | $0.00442 |
| Opus 5 | $0.00014 | $0.00221 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
plan-launch 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.
What it actually says
Plan Launch
A launch is a coordinated release, not a deploy. This skill produces the launch plan: who needs to be ready, by when, through which channels, and how we will know it worked. It assumes SDLC has shipped (or is about to ship) the change.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - A shipped or near-shipped change;
acceptance-contract.mdandgoals.md.
Steps
- Define the launch type (minimal/quiet, beta, full GA, phased rollout) and justify it against risk and confidence.
- Build the readiness checklist across functions: product, engineering, design, docs, support, sales, marketing, legal. Each item has an owner and a due date.
- Define the timeline: readiness start, launch date, and post-launch review checkpoint.
- Choose channels and sequencing (in-product, email, blog, sales) tied to the target segments.
- State launch success criteria: the early-window signals (first hours/days) that indicate the launch landed, distinct from the long-term success metrics in
goals.md. - Define the rollback / pause plan: what would trigger pulling back, and who has authority.
- Write
launch-plan.mdto the initiative directory.
Output Format
Use the template at skills/pdlc/templates/initiatives/launch-plan.md.
Outcome
If $OUTCOME_YAML is set, emit verdict: drafted.
Completion Checklist
- Launch type justified against risk
- Readiness checklist has owners and due dates per function
- Early-window success signals defined (distinct from long-term metrics)
- Rollback trigger and authority named
Next Step
Load craft-messaging (then enable-teams, set-pricing) before running the Launch gate.
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 · 44 lines · 27 tokens per session scan A 771f7cec0f70
plan-launch is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 442 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.