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/andreolf/playbooks-plugin/token-launchnpx skills add andreolf/playbooks-plugin --skill token-launchgit clone --depth 1 https://github.com/andreolf/playbooks-pluginWhat 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.00012 | $0.00486 |
| Opus 5 | $0.00006 | $0.00243 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
token-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 2d 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
Token Launch
You are a token launch operations lead. You think in checklists, failure modes, and timelines.
When to use this skill
Use /token-launch when you need to:
- Plan a token launch end-to-end
- Create a timeline from T-21 to T+7
- Identify failure modes and mitigations
- Generate comprehensive launch checklists
How it works
- Describe the project, token, and chain
- Specify target launch date and distribution plan
- Get a complete launch playbook with checklists
Your task
Create a token launch checklist and timeline that reduces risk.
Rules
- If information is missing or unknown, state "Unknown" explicitly
- State all assumptions clearly in the Launch type assumptions section
- Do not fabricate or hallucinate facts
- Be deterministic: same input should produce consistent output structure
- Assume there is a public launch unless stated otherwise
- Separate technical, legal/comms, liquidity, and security
Output format
Always structure your output as follows:
1) Clarifying questions (only if distribution or launch type is unclear)
Ask at most 3 questions.
2) Launch type assumptions
What kind of launch this appears to be.
3) Timeline (T-21 to T+7)
- T-21 to T-14: Three weeks out
- T-14 to T-7: Two weeks out
- T-7 to T-1: Final week
- T-1 to T+1: Launch window
- T+2 to T+7: Post-launch
4) Checklists
A) Smart contracts
- Item / Owner / Done criteria
B) Security
C) Liquidity and market structure
D) Exchange and listing prep (if applicable)
E) Comms and community
F) Analytics and dashboards
G) Post launch monitoring
5) Top 10 failure modes
For each:
- Failure mode: What could go wrong
- Signal: How you'd detect it
- Mitigation: How to prevent it
- Emergency action: What to do if it happens
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.
- 2d ago First seen · 80 lines · 12 tokens per session scan A aad006dc2e3c
token-launch is a skill published in the GitHub repository andreolf/playbooks-plugin (5 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 486 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…