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.
git clone --depth 1 https://github.com/tjboudreaux/cc-skills-vc-fundraisingWrote 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/commands/tjboudreaux/cc-skills-vc-fundraising/qa-prep)<a href="https://agentmods.dev/commands/tjboudreaux/cc-skills-vc-fundraising/qa-prep"><img src="https://agentmods.dev/badge/commands/tjboudreaux/cc-skills-vc-fundraising/qa-prep/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/commands/tjboudreaux/cc-skills-vc-fundraising/qa-prep"><img src="https://agentmods.dev/badge/commands/tjboudreaux/cc-skills-vc-fundraising/qa-prep.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.00014 | $0.00499 |
| Opus 5 | $0.00007 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
qa-prep 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 11d 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.
What it actually says
Q&A Preparation
You are helping a founder prepare for the toughest questions VCs will ask during their fundraise.
Input
The user provided: $ARGUMENTS
Process
Step 1: Understand the Company
If context is incomplete, ask:
- What does your company do?
- What stage/round are you raising?
- What are your key metrics?
- What do you think your biggest weaknesses are?
- What questions have VCs asked that tripped you up?
Step 2: Identify Top 10 Tough Questions
Launch the qa-coach agent in preparation mode. Instruct it to apply its thinking toolkit: red-team each prepared answer, run a pre-mortem to identify the Q&A moment that would kill the deal, and use inversion to determine which weaknesses to lean into vs. bridge away from. Based on the company's specific situation, identify the 10 toughest questions this founder will face, tailored to:
- Their stage (seed questions differ from Series A)
- Their specific weaknesses
- Their market and competitive dynamics
- Current macro environment
Step 3: Coach Responses
For each question, present:
- The Question
- Why They're Asking -- The underlying concern
- The Trap -- What a bad answer sounds like
- Strong Response -- Using Acknowledge-Bridge-Message framework
- Follow-Up -- What they'll ask next
Step 4: Live Simulation (Optional)
Ask the user if they want to practice live. If yes:
- Play the role of a skeptical VC partner
- Ask questions one at a time
- After each answer, provide coaching feedback
- Score responses on a 1-5 scale
- Focus on areas that need improvement
Step 5: Summary
Provide a cheat sheet:
- The 3 questions you're strongest on
- The 3 questions that need more work
- The #1 question that could kill the deal (from pre-mortem analysis)
- Key phrases to remember
- Red flags to avoid
- Signals to watch for during the live meeting (what to adjust based on VC reactions)
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.
- 11d ago First seen · 61 lines · 14 tokens per session scan A 7ab9363556d8
qa-prep is a command published in the GitHub repository tjboudreaux/cc-skills-vc-fundraising (24 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 499 once invoked, about $0.0001 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 commands, from other repositories
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
synthesise-reviews
Deduplicate and reconcile multiple completed review reports into one prioritised revision plan with conflicts and dependencies made explicit. Use when parallel reviewers have returned findings that need a single action sequence. Not for running the reviews; use $review-cluster.
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
scan
Scan AWS account for cost optimization.
setup
Diagnose-first project setup with state machine — scans, confirms, interviews, writes.