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 floomhq/moto --skill yc-pitch-deckgit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/yc-pitch-deck)<a href="https://agentmods.dev/skills/floomhq/moto/yc-pitch-deck"><img src="https://agentmods.dev/badge/skills/floomhq/moto/yc-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/floomhq/moto/yc-pitch-deck"><img src="https://agentmods.dev/badge/skills/floomhq/moto/yc-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.00087 | $0.01048 |
| Opus 5 | $0.00044 | $0.00524 |
| Sonnet 5 | $0.00017 | $0.00210 |
| Haiku 4.5 | $0.00009 | $0.00105 |
Grade A, and why
yc-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 7d 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.
YC Pitch Deck
Core Philosophy
Lead with whatever is most impressive. Clarity beats accuracy (80% accurate, 100% clear > 100% accurate, 80% clear). Every slide supports ONE idea. Investors spend ~10 seconds per slide.
Slide Structure (7-10 slides)
1. Title
- Company name + one-liner (max 10 words)
- Must pass the "mom test": can a non-technical person understand what you do?
- Bad: "Revolutionizing the paradigm of cloud-native microservice orchestration"
- Good: "The app store for microservices"
- Include: stage, founder name, date. Nothing else.
2. Problem
- Max 3 pain points. Each must be visceral and specific, not abstract.
- Use the P.A.I.N. framework: Problem, Audience, Impact, Non-obvious insight
- Bad: "Deployment is inefficient and outdated"
- Good: "12M vibecoders build apps daily. <1% ever get deployed. Zero marketplaces exist."
- Include real data, quotes, or specific examples. No opinions.
- The insight (what everyone else missed) is the most important part.
3. Solution
- One headline benefit (max 12 words)
- Show the product, not a description. Screenshot, demo, or UI mockup.
- 2-3 bullet outcomes (what changes for the user), not features
- Bad: "Cloud-based platform with auto-scaling and CI/CD pipeline integration"
- Good: "Push code, get a live URL with payments. 45 seconds."
4. How It Works (optional but powerful)
- 3-step flow maximum. Each step: verb + outcome
- Show the actual UI/CLI/flow, not a diagram of boxes and arrows
- End with the result: "From X to Y in Z time"
5. Market + Timing
- Bottom-up TAM, not top-down. Show the math.
- Bad: "$180B cloud market, we capture 0.5%"
- Good: "12M vibecoders x $20/mo avg spend = $2.9B SAM. 50K early adopters x $20 = $12M SOM year 1"
- "Why now?" is critical: what changed that makes this possible TODAY?
- Include 2-3 comparable companies with valuations to anchor investor mental models
6. Business Model
- One sentence: how you make money
- Airbnb: "10% commission on each transaction" (that's it)
- Show pricing tiers or unit economics if they're compelling
- If marketplace: show both sides (take rate, seller earnings)
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.
- 7d ago First seen · 88 lines · 87 tokens per session scan A fcfc1ffd434e
yc-pitch-deck is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 3mo ago), licensed MIT. It adds 87 tokens to every session and 1,048 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
memstack-business-financial-model
Use this skill when the user says 'financial model', 'projections', 'revenue forecast', 'unit economics', 'break-even', 'cash flow', or mentions MRR, churn, CAC, LTV, or runway. Builds monthly projections with scenario modeling. Do NOT use for pricing strategy or invoice generation.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.