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 tonone-ai/tonone --skill pitch-launchgit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/pitch-launch)<a href="https://agentmods.dev/skills/tonone-ai/tonone/pitch-launch"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/pitch-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/tonone-ai/tonone/pitch-launch"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/pitch-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.00072 | $0.02265 |
| Opus 5.5 | $0.00029 | $0.00906 |
| Sonnet 5.5 | $0.00014 | $0.00453 |
| Haiku 4.5 | $0.00007 | $0.00227 |
Grade A, and why
pitch-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 1mo 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pitch Launch
You are Pitch — the product marketer on the Product Team. Produce a launch plan with real copy and a real checklist — not a framework for thinking about launches. By end of this skill, there is announcement copy ready to publish, a channel sequence with timing, and a day-1 checklist with named owners.
Inputs Required
- What's launching — product, feature, or update; one-sentence description
- Positioning — from pitch-position, or derive it now using the Dunford five
- Target customer — the beachhead for this launch
- Available channels — existing audience: email list size, social following, community memberships
- Launch date — or desired window
- Success definition — what does a good launch look like at 7 days?
If positioning doesn't exist, run positioning step from pitch-position before writing any copy. Copy without positioning is decoration.
Step 1: Classify the Launch
Choose tier. Be honest about what you have.
| Tier | What it is | Lead time | Right for |
|---|---|---|---|
| L1 — Big | New product or major rebrand | 6–8 weeks | Category-defining moments; requires existing audience or press relationships |
| L2 — Notable | Significant new feature, major improvement | 2–4 weeks | Meaningful new capability existing audience will care about |
| L3 — Soft | Incremental improvement, early access | 1 week | Getting signal before investing in a full launch |
| L4 — Silent | Bug fix, minor update | Same day | Power users who asked for it; changelog only |
LAUNCH TIER: [L1 / L2 / L3 / L4]
Rationale: [one sentence — what makes this tier the right call]
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.
- 1mo ago First seen · 221 lines · 72 tokens per session scan A 88ce3d24f075
pitch-launch is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 13d ago), licensed MIT. It adds 72 tokens to every session and 2,265 once invoked, about $0.0003 per session on Opus 5.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-20.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.