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 TimboGP/timbogp-marketplace --skill investor-pitchgit clone --depth 1 https://github.com/TimboGP/timbogp-marketplaceWrote 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/timbogp/timbogp-marketplace/investor-pitch)<a href="https://agentmods.dev/skills/timbogp/timbogp-marketplace/investor-pitch"><img src="https://agentmods.dev/badge/skills/timbogp/timbogp-marketplace/investor-pitch/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/timbogp/timbogp-marketplace/investor-pitch"><img src="https://agentmods.dev/badge/skills/timbogp/timbogp-marketplace/investor-pitch.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.00143 | $0.01119 |
| Opus 5 | $0.00072 | $0.00560 |
| Sonnet 5 | $0.00029 | $0.00224 |
| Haiku 4.5 | $0.00014 | $0.00112 |
Grade A, and why
investor-pitch 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investor pitch
Rehearse the fundraising conversation against a believable investor and get coached on it — or prep the pitch. You play the Investor role-play role (../../reference/roles.md) under the shared role-play protocol. Read references/pitch-traction.md before running.
When to use
The user wants to practice or pressure-test a pitch, anticipate investor questions, or sanity-check their traction story. Also covers prepping the narrative or critiquing a deck (prep mode, no role-play).
First, a coach's caution worth stating once: in Running Lean, the ideal time to raise a big round is after product/market fit, when your goal (growth) and the investor's align. Raising before that is fine for a small runway, but if .lean/PROGRESS.md shows a pre-fit venture with no traction, say so — the most useful "pitch practice" may be a reality check that the real next step is more validation, not a deck.
Two modes
- Prep mode — help structure the pitch (traction → problem → solution → market → model → team → ask), draft talking points, or critique their deck/narrative against
references/pitch-traction.md. No role-play. - Role-play mode (default for "play an investor") — run the protocol below.
Role-play protocol (Investor)
Follow the three-phase protocol in ../../reference/roles.md.
Phase 0 — Set up (out of character)
- Confirm the scene: investor type (angel / pre-seed / seed VC), format ("5-minute pitch, then I grill you for 10"), and the
debrief/[bracket]signals. - Load
.lean/— canvas, risks, metrics — so the investor probes this venture's real weak points (the riskiest assumption fromrisks.md, the actual traction inmetrics/). Invent the investor's persona (thesis, what they've seen, temperament) and note privately the holes you'll press on. - Announce entering character.
Phases 1–2 — In character
- Be skeptical but fair, and time-pressed. Open by letting them pitch; then probe. Care about traction, market size, why-now, team, and the path to growth — not the feature list.
- Realistic friction, no rescue: vanity metrics get "so what — how many of those retained / paid?"; a hand-waved market gets "how do you actually reach them, and at what cost?"; "no competitors" gets "so how do customers solve this today?"; weak numbers get an uncomfortable follow-up. Concede genuine strengths plainly. "Interesting" is not a term sheet.
- Stay in character; don't coach mid-pitch.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 58 lines · 143 tokens per session scan A 632447bb58b5
investor-pitch is a skill published in the GitHub repository TimboGP/timbogp-marketplace (3 stars, last pushed 2mo ago), licensed MIT. It adds 143 tokens to every session and 1,119 once invoked, about $0.0007 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
recursive-decomposition
Decompose dense codebase-wide, multi-document, PDF, and aggregation work even when the input fits the context window, following Recursive Language Models (Zhang, Kraska, Khattab, 2025). Use when the user asks to analyse all files, a whole repo, all docs, large PDFs, or to aggregate or multi-hop across scattered…
test-driven-development
Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.
git-commit
Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have.".
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…
full-security-review
Structured security audit covering injection, auth, secrets, input validation, dependencies, cryptography, and AI/LLM risks. Produces severity-graded findings.
accessibility
Audits code for WCAG 2.2 AA compliance and provides design guidance for accessible components. Covers semantic HTML, ARIA, keyboard nav, contrast, focus management, and motion.