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 user-buyer-bridgegit 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/user-buyer-bridge)<a href="https://agentmods.dev/skills/brennanjcollins/unabatedpm-coaching/user-buyer-bridge"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/user-buyer-bridge/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/user-buyer-bridge"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/user-buyer-bridge.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.00064 | $0.04899 |
| Opus 5 | $0.00032 | $0.02449 |
| Sonnet 5 | $0.00013 | $0.00980 |
| Haiku 4.5 | $0.00006 | $0.00490 |
Grade B, and why
User-Buyer Bridge Coach scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Ask questions to fill in each blank. Don't lecture — guide me to discover the connections. How it starts
The opening of the file, as written. The whole thing — 508 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 user-buyer bridging interactively. Triggered by direct invocation or natural conversation.
Evaluate mode: Read a document silently, score its bridge 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 pitch, business case, or product 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:
-
Market & customer intelligence — Does the document speak user language AND buyer language? Is the user need quantified (how many users affected, how long does the problem take)? Is the buyer impact quantified (revenue at risk, cost to solve, competitive threat)? Or is it user-only language with assumed buyer benefit?
-
Sales enablement — Can you trace the path from user need → buyer economics? Does it address "What Would Get Them Fired?" (what outcome matters to the buyer's boss)? Does it distinguish user pain from buyer value (users want speed, buyers want throughput)? Are there buyer objections addressed (pricing, implementation, risk)? Or does it assume buyers care about the same things users care about?
Red flags to check:
- Only user language ("users love this feature")
- Missing buyer economics or ROI quantification
- Assuming buyers care about ease-of-use instead of results
- "Willingness to pay" unaddressed
- Vague language ("improves efficiency" without numbers)
- No competitive alternative comparison
- Missing buyer persona (don't know who decides)
Return format:
SKILL: User-Buyer Bridge
CATEGORIES SCORED:
- Market & customer intelligence: [X]/5
Evidence: "[exact quote from document]"
Gap: [what's missing — quantified user need, buyer impact, or user persona]
Upgrade: [single highest-leverage change]
- Sales enablement: [X]/5
Evidence: "[exact quote from document]"
Gap: [what's missing — buyer language, ROI, objection handling, or persona clarity]
Upgrade: [single highest-leverage change]
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 · 508 lines · 64 tokens per session scan B ebbcffeff83a
User-Buyer Bridge Coach is a skill published in the GitHub repository BrennanJCollins/UnabatedPM-coaching (4 stars, last pushed 22d ago), licensed MIT. It adds 64 tokens to every session and 4,899 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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.