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/BrennanJCollins/UnabatedPM-coachingWrote 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/brennanjcollins/unabatedpm-coaching/coach-pitch)<a href="https://agentmods.dev/commands/brennanjcollins/unabatedpm-coaching/coach-pitch"><img src="https://agentmods.dev/badge/commands/brennanjcollins/unabatedpm-coaching/coach-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/commands/brennanjcollins/unabatedpm-coaching/coach-pitch"><img src="https://agentmods.dev/badge/commands/brennanjcollins/unabatedpm-coaching/coach-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.00037 | $0.00854 |
| Opus 5 | $0.00018 | $0.00427 |
| Sonnet 5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
Coach 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 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are guiding me through a complete pitch development workflow using three coaching frameworks from The Influential PM course by Brennan Collins. Work through each step in sequence, completing one before moving to the next.
Here is my pitch context:
[Paste your context here. The more specific detail you provide — your product, audience, current situation, and what you have so far — the better the coaching.]
Step 1: Strategic Storytelling
Start by coaching me to build a compelling pitch using Brennan's story structure:
- The Stakes: What's at risk if nothing changes? (Business problem, not feature gap)
- The Villain: What's causing the problem? (Market force, competitor, internal friction)
- The Journey: What did we discover? (Customer insight, data, pattern)
- The Solution: How does our work address this? (Connected to stakes, not feature list)
- The Evidence: Why should they believe us? (Customer name, metric, outcome)
- The Ask: What do we need from them? (Decision, resources, meeting)
Rate my pitch: Is it a feature report ("We built X"), a status update ("X is going well"), or a strategic story ("Here's why X matters to the business")? Only strategic stories get to "yes."
When my story structure is compelling, summarize and move to Step 2.
Step 2: Cafe Update Compression
Now compress the full pitch into a 60-second Cafe Update using the 5-Part Structure:
- Quick Context (5-10 sec): Reference something THEY care about
- Recent Win (10-15 sec): Named customer, specific number, real outcome
- Strategic Insight (10-15 sec): Scale from one win to business-level insight
- Engaging Ask (10-15 sec): Request a strategic conversation, not a demo
- Graceful Close (5 sec): End clean, leave them wanting more
Apply the "What Would Get Them Fired?" test: Does my opener reference the listener's biggest professional risk?
Rate it Good / Better / Best:
- Good: Accurate but forgettable. They'll nod and forget.
- Better: Has structure and a proof point, but opens with MY work not THEIR problem.
- Best: Opens with their world, makes my work relevant, creates a meeting.
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 · 76 lines · 37 tokens per session scan A 930080aee10c
Coach Pitch is a command published in the GitHub repository BrennanJCollins/UnabatedPM-coaching (4 stars, last pushed 21d ago), licensed MIT. It adds 37 tokens to every session and 854 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 commands, from other repositories
review
Submit a story for verification (In Progress → In Review, no PR yet).
audit
Adversarial, exhaustive review of the entire repository across code, tests, documentation, and configuration, with optional fixing in the same run. Assumes the code is incorrect until proven otherwise. This is the default command when the invocation names no other.
wp-cleanup
Find and clean up unused PHP code, Composer dependencies, imports, and dead code in WordPress projects.
prep
Prepare a pre-meeting briefing by reviewing all memory files and surfacing items that need discussion.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.