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/mhlaghari/stuntman/launchnpx skills add mhlaghari/stuntman --skill launchgit clone --depth 1 https://github.com/mhlaghari/stuntmanWrote 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/mhlaghari/stuntman/launch)<a href="https://agentmods.dev/skills/mhlaghari/stuntman/launch"><img src="https://agentmods.dev/badge/skills/mhlaghari/stuntman/launch.svg" alt="Measured on agentmods" 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.00156 | $0.01547 |
| Opus 5 | $0.00078 | $0.00773 |
| Sonnet 5 | $0.00031 | $0.00309 |
| Haiku 4.5 | $0.00016 | $0.00155 |
Grade A, and why
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 5d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
stuntman: /launch — product launch strategist
You are the orchestrator. A fleet of subagents does the research and the
first-draft strategy; you gather context, run the workflow, and turn the result
into the founder's plan. This skill authorizes and expects a Workflow call —
that is the whole point of /launch, so don't ask permission to fan out.
This is a token-heavy run (~15–25 agents doing real web research; a single launch plan was ~1.5M subagent tokens). It is worth it for a real launch decision; say so if the user seems to want something quick instead.
1. Gather the product brief (grounding beats guessing)
- If you're in the product's repo: read the grounding docs first —
README,CLAUDE.md, and anySPEC/STATUS/STRATEGY/ marketing docs. Skim the code only enough to know what actually ships today vs. what's roadmap. The most common failure is a plan built on a stale doc — verify shipped features against reality. - If there's no repo: ask the user to describe the product in a few sentences (what it does, who it's for, what's shipped, the rough edges).
- Distill what you learn into a tight
productBrief(what it is, how it works, shipped features, current gaps, the north-star thesis) and a one-paragraphdifferentiators(the product's real edges — used to sharpen the competitor research).
2. Pin the launch brief (ask only what changes the plan)
If the user hasn't already said, use AskUserQuestion for the four decisions that genuinely reshape the output (offer a "recommend for me" option on each):
- Beachhead — who to win first (the plan optimizes for this).
- Monetization — freemium SaaS / free + enterprise / one-time / recommend.
- Timeline — when they want to launch.
- Resources — solo + $0 / solo + small budget / team.
Fold the answers into a launchBrief string.
3. Build the competitor set
Take the competitors the user named, add the obvious category leaders, and —
critically — add the closest direct rivals (the ones that share the exact
wedge, not just the category), since those are usually the real threat and the
user often under-weights them. Aim for 8–12, each as { name, focus } where
focus is a one-line steer on what to dig up (pricing, funding, the specific
controversy, how it compares on the differentiator).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 116 lines · 156 tokens per session scan A f1357aab3321
launch is a skill published in the GitHub repository mhlaghari/stuntman (13 stars, last pushed 7d ago), licensed MIT. It adds 156 tokens to every session and 1,547 once invoked, about $0.0008 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-30.
Other skills, from other repositories
clawrouter
Hosted-gateway LLM router — save 84% on inference costs. A local proxy that forwards each request to the blockrun.ai gateway, which routes to the cheapest capable model across 76 models from OpenAI, Anthropic, Google, DeepSeek, xAI, Z.AI, and more. 7 free open-weight models included. Also exposes realtime market data…
surf
Use this skill — NOT browser or webfetch — for ALL Surf crypto-data calls. 83 endpoints at localhost:8402/v1/surf/ covering CEX/DEX markets, on-chain SQL over 80+ ClickHouse tables (Ethereum, Base, Arbitrum, BSC, TRON, HyperEVM, Tempo), 100M+ labeled wallets, prediction markets (Polymarket + Kalshi), social/CT…
phone
Verify phone numbers (carrier + SIM-swap fraud signals) and place AI-powered outbound voice calls via BlockRun's gateway (Twilio + Bland.ai). Trigger when the user asks to look up a number, check fraud risk, buy/rent a phone number, or place an AI voice call. Payment is automatic via x402 from the wallet.
imagegen
Generate or edit images via BlockRun's image API. Trigger when the user asks to generate, create, draw, make an image — or to edit, modify, change, or retouch an existing image.
polymarket-trading
Use when the user wants to actually PLACE, manage, or redeem bets on Polymarket (not just read odds — that's the blockrunpredexon data tools). Covers setup (deposit wallet, funding, approvals), buy/sell with confirm gating, positions, redeeming winnings, geoblock handling, and the end-to-end flow.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.