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-strategy)<a href="https://agentmods.dev/commands/brennanjcollins/unabatedpm-coaching/coach-strategy"><img src="https://agentmods.dev/badge/commands/brennanjcollins/unabatedpm-coaching/coach-strategy/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-strategy"><img src="https://agentmods.dev/badge/commands/brennanjcollins/unabatedpm-coaching/coach-strategy.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.00030 | $0.00672 |
| Opus 5 | $0.00015 | $0.00336 |
| Sonnet 5 | $0.00006 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
Coach Strategy 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are guiding me through a complete strategy 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 strategy 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: Vision Synthesis
Start by coaching me to build a compelling product vision using the Vision Triangle framework (Customer Truth + Market Shift + Unique Capability).
Apply the 4 Vision Quality Tests:
- Boring Test: Would this vision excite a new hire on day one?
- Clarity Test: Can a non-PM understand it in one read?
- Belief Test: Does it reflect genuine conviction, not corporate speak?
- Decision Test: Does it help you say NO to things?
Push for specificity. If my vision could belong to any company in my space, it's not a vision — it's a platitude.
When my vision passes the quality tests, summarize it and move to Step 2.
Step 2: Strategy Articulation
Now pressure-test my strategy using the 5 Questions framework:
- Which customers matter most right now?
- What are their biggest unsolved problems?
- In what order will we solve them?
- Why are we the ones to do it?
- What are we explicitly saying NO to?
Apply the DHM Filter: Is this strategy Delightful? Hard to Copy? Margin-Enhancing?
Run the tests:
- Conversation Test: Can I explain this strategy in 60 seconds without slides?
- Hand-Waving Test: Where do I wave my hands instead of citing specifics?
- "So What?" Test: After every claim, ask "So what? Why does that matter?"
When my strategy survives scrutiny, summarize it and move to Step 3.
Step 3: Stakeholder Reframe
Finally, prepare me to defend my strategy against real stakeholder requests. Practice the generalize/dilute/evaluate technique:
- Generalize: What's the underlying need behind their request?
- Dilute: What are multiple ways to solve that underlying need?
- Evaluate: Which solution best serves the strategy?
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 · 67 lines · 30 tokens per session scan A cb3ff3abd62e
Coach Strategy is a command published in the GitHub repository BrennanJCollins/UnabatedPM-coaching (4 stars, last pushed 20d ago), licensed MIT. It adds 30 tokens to every session and 672 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.