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 BrennanJCollins/UnabatedPM-coaching --skill product-objective-definitiongit 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/skills/brennanjcollins/unabatedpm-coaching/product-objective-definition)<a href="https://agentmods.dev/skills/brennanjcollins/unabatedpm-coaching/product-objective-definition"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/product-objective-definition/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/brennanjcollins/unabatedpm-coaching/product-objective-definition"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/product-objective-definition.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.00049 | $0.06157 |
| Opus 5 | $0.00024 | $0.03078 |
| Sonnet 5 | $0.00010 | $0.01231 |
| Haiku 4.5 | $0.00005 | $0.00616 |
Grade A, and why
Product Objective Definition Coach 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 — 640 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating Modes
This skill operates in two modes:
Conversation mode (default): Coach the PM through objective definition interactively. Triggered by direct invocation or natural conversation.
Evaluate mode: Read a document silently, score its objective rigor, and return structured findings. No conversation, no questions — just assessment. Triggered by the /audit orchestrator.
Evaluate Mode Instructions
When invoked in evaluate mode, you receive a product roadmap, strategy, or objective document. Do NOT coach. Do NOT ask questions. Read and score.
Score each dimension 1-5:
- 1 = Not present or fundamentally broken
- 2 = Attempted but significant gaps
- 3 = Competent but missing key elements
- 4 = Strong with minor improvements possible
- 5 = Exemplary — would pass CFO review
Dimensions to evaluate:
-
Problem & solution definition — Are objectives outcome-oriented or feature-focused? Can you distinguish what's being built (feature level) from why (objective level)? Are objectives measurable with specific targets? Is there a Bridge Madlib connecting user benefit to business outcomes? Or are features disguised as objectives with vague success criteria?
-
Solution validation & optimization — Does the document show a Reverse 5 Whys chain from feature to business outcome? Are business metrics quantified (conversion rate, churn rate, ARR impact)? Does the document address how success will be validated? Is there a baseline and target? Or is there a single feature with unmeasurable user benefit?
Red flags to check:
- Features disguised as objectives ("Build a dashboard")
- Vague success criteria ("improve user experience")
- Objectives missing persona ("Increase conversion" without stating from where)
- No business metric connection (user goal only, no revenue/retention impact)
- Unmeasurable outcomes ("make users happy")
- Missing baseline and target (target without knowing current state)
- Bridge Madlib absent (stating what to build, not user benefit to business outcome)
- No validation plan for assumptions
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 · 640 lines · 49 tokens per session scan A 30a265b01d5c
Product Objective Definition Coach is a skill published in the GitHub repository BrennanJCollins/UnabatedPM-coaching (4 stars, last pushed 21d ago), licensed MIT. It adds 49 tokens to every session and 6,157 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
pm-brand-motion
A guided process for defining a brand's motion style and making a logo animation demonstration.
pm-brainstorm
A guided brainstorming workflow for exploring a new product idea before detailed research or requirements work. It collects basic information about the product, users, and problem through staged questions.
pm-search
A workflow for collecting market research, competitor information, industry discussion, and compliance-policy data using an external search tool.
pm-aarrr
A post-launch product-growth workflow based on AARRR: acquiring users, activating them, retaining them, earning revenue, and gaining referrals.
start-super-pm
Use when starting any product management task - automatically detects task type and invokes appropriate PM skill using intelligent routing.
pm-demand
A product-research workflow that gathers information about users, their problems, and a product idea before writing a research report. Brainstorming means generating and exploring possible ideas first.