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 mfwarren/entrepreneur-claude-skills --skill pitch-deckgit clone --depth 1 https://github.com/mfwarren/entrepreneur-claude-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/mfwarren/entrepreneur-claude-skills/pitch-deck)<a href="https://agentmods.dev/skills/mfwarren/entrepreneur-claude-skills/pitch-deck"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/pitch-deck/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/mfwarren/entrepreneur-claude-skills/pitch-deck"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/pitch-deck.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.00003 | $0.00598 |
| Opus 5 | $0.00002 | $0.00299 |
| Sonnet 5 | $0.00001 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
pitch-deck 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 12d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pitch Deck
Investor pitch deck structure, narrative arc, and slide-by-slide content.
Purpose
Create a compelling pitch deck that tells your startup's story and makes investors want to learn more. Focus on narrative, not slide design.
Workflow
Step 1: Gather Context
- Company, product, and stage
- What you're raising and at what valuation
- Traction metrics
- Team background
- Use of funds
Step 2: Deck Structure (10-12 slides)
- Title: Company name, one-line description, your name
- Problem: The pain point (make it visceral)
- Solution: How you solve it (demo-worthy)
- Market: TAM/SAM/SOM (credible, not fantasy)
- Product: How it works (screenshots, demo)
- Traction: Growth metrics, revenue, users, key milestones
- Business Model: How you make money
- Competition: Positioning map (why you win)
- Team: Why you're the team to do this
- Financials: Key metrics and projections
- Ask: How much you're raising, use of funds, milestones
- Appendix: Supporting data (optional)
Step 3: Write Slide Content
For each slide: headline, 3-5 bullet points or a key visual description, and speaker notes.
Step 4: Narrative Check
The deck should tell a story:
- Problem is painful → Solution is elegant → Market is huge → You're winning → Team can execute → Now is the time
Step 5: Common Mistakes Review
Flag issues:
- Too many slides
- No clear ask
- Unsubstantiated TAM
- Team slide missing relevant experience
- No traction data
Output Format
## Pitch Deck: [Company Name]
### Slide 1: Title
**Headline:** [text]
**Content:** [bullet points]
**Speaker notes:** [what to say]
[Continue for each slide]
### Narrative Arc
[Story summary]
Constraints
- 10-12 slides maximum — if you need more, you're not focused enough
- Every number must be defensible
- Don't make claims about market size without showing the math
- Be honest about stage and traction — investors see through exaggeration
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.
- 12d ago First seen · 88 lines · 3 tokens per session scan A fc57edb9f3b7
pitch-deck is a skill published in the GitHub repository mfwarren/entrepreneur-claude-skills (67 stars, last pushed 7mo ago), licensed MIT. It adds 3 tokens to every session and 598 once invoked, about $0.0000 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
modelchk
Size a task's run before spending it: the cheapest sufficient capability tier (fast, standard, frontier) and the reasoning effort within it, on a neutral scale that binds to whatever levels the model exposes. Use when work seems over- or under-powered, costly, ambiguous, or high-risk, or asks which model class and how…
re0-loop
Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting code die. Use for long agentic projects where progress must be measured by quality-cleared templates, reusable modules, and eliminated anti-patterns rather than hours spent or features accumulated.
autobahn
Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved prompt, never the risky input. Use when a task includes stealth, scraping, privacy, IP, policy, licensing, security, or…
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
ssotize
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts…
re0-plan
Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.