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 Dokkabei97/forged-claude-code --skill pitch-deckgit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/pitch-deck)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/pitch-deck"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/pitch-deck.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.00034 | $0.01339 |
| Opus 5 | $0.00017 | $0.00669 |
| Sonnet 5 | $0.00007 | $0.00268 |
| Haiku 4.5 | $0.00003 | $0.00134 |
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 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pitch Deck - Presentation Storyline Designer
Overview
Crafts compelling pitch deck narratives. A great pitch deck doesn't just inform — it makes the audience believe in your vision. Content and story first, slides second.
1. When to Apply
| Trigger | Behavior |
|---|---|
| Fundraising preparation | Investor pitch deck |
| Partner outreach | Partnership deck |
| Enterprise sales | Sales deck |
| "pitch deck", "피치덱" | Interactive deck builder |
2. Investor Pitch Deck (12 slides)
## Slide 1: Title
**Content**: Company name, tagline, your name, date
**Key message**: One sentence that captures what you do
## Slide 2: Problem
**Content**: The pain you're solving
**Key message**: Make them FEEL the problem
**Tips**:
- Use a specific story or scenario
- Quantify the pain ($, time, frustration)
- "X million people face this problem every day"
## Slide 3: Solution
**Content**: Your product in action
**Key message**: How you solve the problem differently
**Tips**:
- Demo screenshot or product visual
- Show, don't tell
- Keep it simple — one core value proposition
## Slide 4: How It Works
**Content**: 3-step process or product flow
**Key message**: It's not magic — here's the mechanism
**Tips**:
- Maximum 3 steps
- Visual flow diagram preferred
- Focus on user experience, not technology
## Slide 5: Traction / Validation
**Content**: Metrics that prove momentum
**Key message**: This is already working
**Data points**: Revenue, users, growth rate, retention, NPS
**Tips**:
- Up-and-to-the-right chart
- If pre-revenue: waitlist, LOIs, partnerships, user engagement
- Highlight growth RATE, not just absolute numbers
## Slide 6: Market Size
**Content**: TAM → SAM → SOM with sources
**Key message**: The opportunity is massive
**Tips**:
- Bottom-up calculation > top-down
- SAM/SOM are more important than TAM
- Cite credible sources
## Slide 7: Business Model
**Content**: How you make money
**Key message**: Clear path to revenue
**Tips**:
- Pricing tiers if SaaS
- Unit economics (LTV, CAC, margins)
- Expansion revenue strategy
## Slide 8: Competition
**Content**: Positioning matrix (NOT a feature comparison)
**Key message**: Why you win in your specific niche
**Tips**:
- 2x2 matrix with meaningful axes
- Don't say "no competitors" (red flag)
- Show your unique position
## Slide 9: Team
**Content**: Founders + key hires
**Key message**: Why THIS team will win
**Tips**:
- Relevant experience (domain expertise, exits)
- Team completeness (tech + business + domain)
- Photos + name + one-line credential
## Slide 10: Financials
**Content**: Revenue projections (3 years), key assumptions
**Key message**: Credible path to scale
**Tips**:
- Bottom-up projections, not top-down
- Show key assumptions explicitly
- Include current burn rate and runway
## Slide 11: The Ask
**Content**: Amount, use of funds, milestones this enables
**Key message**: Here's what we need and what we'll achieve
**Tips**:
- Specific amount (range OK: "$2-3M")
- 3-4 use of funds categories with percentages
- Milestones this funding achieves (18 months)
## Slide 12: Contact
**Content**: Thank you, contact info, CTA
**Key message**: Let's continue the conversation
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 · 195 lines · 34 tokens per session scan A e1c39af07437
pitch-deck is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 1,339 once invoked, about $0.0002 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-31.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.
vellum-skills-catalog
Discover bundled skills and search/install community skills from the skills.sh registry.