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 exiao/pm-skills --skill pitch-creatorgit clone --depth 1 https://github.com/exiao/pm-skillsWrote 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/exiao/pm-skills/pitch-creator)<a href="https://agentmods.dev/skills/exiao/pm-skills/pitch-creator"><img src="https://agentmods.dev/badge/skills/exiao/pm-skills/pitch-creator/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/exiao/pm-skills/pitch-creator"><img src="https://agentmods.dev/badge/skills/exiao/pm-skills/pitch-creator.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.00137 | $0.02219 |
| Opus 5.5 | $0.00055 | $0.00888 |
| Sonnet 5.5 | $0.00027 | $0.00444 |
| Haiku 4.5 | $0.00014 | $0.00222 |
Grade A, and why
pitch-creator scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -o /dev/null -w "%{http_code}\n" https://pitch-<slug>.surge.sh # 504 first is normal, wait 8s How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pitch Creator
Output rule (overrides everything below): communicating simply and concisely is the single most important thing this skill does. Total text across the whole pitch is one page max. If the pitch needs more than that to land, the extra weight goes into diagrams, prototypes, or visuals, never more prose. Text states the decision (proposal, problem, recommendation); artifacts carry everything else. If you're writing a fourth paragraph of explanation, you owe a prototype or a diagram instead. A pitch that's a wall of text has failed even if every section is present.
Turn a rough product idea into a decision-ready pitch. The output exists to help someone say yes or no, so every section either moves that decision or gets cut.
The funnel this optimizes: acquisition → activation → engagement → retention → monetization → referral. Adapt the exact stage names to your product's own funnel if it differs. Every pitch names which arrow it's trying to move. A pitch that can't point to one arrow is a solution looking for a problem.
The two non-negotiables
Most weak pitches fail the same two ways, so the skill forces the fix:
- Solutions are prototypes, not adjectives. "A cleaner onboarding" is not a solution, it's a wish. Section 3 must contain things a person can click, look at, or run: a real HTML/interactive prototype, a screenshot, a Figma-style mock, a code stub. If you describe a solution in words, you haven't designed it yet. Build the artifact.
- Placement is a diagram, not a sentence. "This helps during onboarding" tells the reader nothing about what it displaces or what comes before and after. Section 4 must be an actual storyboard/flow diagram (SVG rendered to PNG, or an image), showing the before flow and the after flow with the change marked. See "Diagrams" below.
If you find yourself typing a paragraph where a prototype or diagram belongs, stop and make the artifact instead.
When the solution is thin glue over existing APIs
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.
- 2mo ago First seen · 106 lines · 137 tokens per session scan A bd5dcfea2e67
pitch-creator is a skill published in the GitHub repository exiao/pm-skills (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 137 tokens to every session and 2,219 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…