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 confidence-scenario-simulatorgit 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/confidence-scenario-simulator)<a href="https://agentmods.dev/skills/brennanjcollins/unabatedpm-coaching/confidence-scenario-simulator"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/confidence-scenario-simulator/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/confidence-scenario-simulator"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/confidence-scenario-simulator.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.00071 | $0.02683 |
| Opus 5.5 | $0.00028 | $0.01073 |
| Sonnet 5.5 | $0.00014 | $0.00537 |
| Haiku 4.5 | $0.00007 | $0.00268 |
Grade A, and why
Confidence Scenario Simulator 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 1mo 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 — 215 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): Simulate high-stakes scenarios with realistic pushback, play stakeholder roles, and coach on confidence signals. Triggered by direct invocation or natural conversation.
Evaluate mode: Read a written document silently (pitch deck, exec update, written proposal), score confidence signals in the writing itself, 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 deck, executive update, proposal, or stakeholder communication. Do NOT coach. Do NOT ask questions. Read and score confidence signals in the writing.
Score each dimension 1-5:
- 1 = Not present or fundamentally broken (excessive hedging, tentative)
- 2 = Attempted but undercuts confidence (qualifiers, weak language)
- 3 = Competent but could be stronger (some hedging, could be more declarative)
- 4 = Strong with clear conviction and evidence
- 5 = Exemplary — authoritative, evidence-backed, shows earned confidence
Dimensions to evaluate:
-
Messaging & communication — Does the PM hedge or qualify excessively ("I think we could potentially...")? Does the writing use uptalk-equivalent language (questions instead of statements)? Is there excessive use of qualifiers ("sort of," "kind of," "just," "maybe")? Does it show conviction when evidence supports it? Are statements declarative or tentative?
-
Stakeholder alignment — Does the document show authority signals through specificity and evidence? Does it position the PM as a strategic thinker or apologetically proposing ideas? Does it acknowledge trade-offs (strong) or overexplain concerns (weak)? Does it use "we believe" with evidence or "I think maybe"?
Red flags to check:
- Excessive hedging ("potentially," "I think," "maybe," "kind of," "sort of")
- Questions instead of statements ("Shouldn't we consider...?" instead of "We should...")
- Over-qualifying every claim ("While I could be wrong, it seems like...")
- Apologetic framing ("I know this is probably not a big deal, but...")
- Seeking permission instead of stating position ("Do you think we could...?" instead of "We should...")
- Tentative language on claims with strong evidence
- No confidence even where data clearly supports it
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.
- 1mo ago First seen · 215 lines · 71 tokens per session scan A 6b32d5d76f7e
Confidence Scenario Simulator is a skill published in the GitHub repository BrennanJCollins/UnabatedPM-coaching (5 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 2,683 once invoked, about $0.0003 per session on Opus 5.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-data
A workflow for defining product metrics, tracking events, monitoring results, and planning data analysis.
scenario-zbrush-expert
Use when an agent drives Maxon ZBrush 2026 for any task (sculpt in ZBrush, DynaMesh, ZRemesher, UVs, export, polypaint, posing, 3D print, clean up an AI mesh in ZBrush), when writing ZBrush Python (zbrush.commands) or ZScript, when the ZBrush bridge is not answering, a palette path or set() does nothing, a scripted…
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
explorer-pipeline
Use when asked to make an interactive 3D explorer of a topic from start to finish, go from a topic to a clickable 3D learning page, or run the whole 3D explorer process. Produces a staged run of explorer-interface-brief, model-prompt-pack and explorer-viewer-builder in order for one topic, with the hand-offs between…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain — personal notes go there, not here. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/)…