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 first-90-days-playbookgit 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/first-90-days-playbook)<a href="https://agentmods.dev/skills/brennanjcollins/unabatedpm-coaching/first-90-days-playbook"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/first-90-days-playbook/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/first-90-days-playbook"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/first-90-days-playbook.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.00070 | $0.03548 |
| Opus 5 | $0.00035 | $0.01774 |
| Sonnet 5 | $0.00014 | $0.00710 |
| Haiku 4.5 | $0.00007 | $0.00355 |
Grade A, and why
First 90 Days Playbook 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 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.
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 — 292 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 building a 90-day onboarding plan using the absorb-then-direct sequence. Triggered by direct invocation or natural conversation.
Evaluate mode: Read an onboarding plan, 30/60/90 plan, or transition document silently, score its adherence to the framework, 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 90-day plan, onboarding document, or transition strategy. Do NOT coach. Do NOT ask questions. Read and score.
Score each dimension 1-5:
- 1 = Not present or fundamentally broken (jumping to directing, skipping absorption)
- 2 = Attempted but significant gaps (skipping phases, no customer immersion)
- 3 = Competent but sequencing issues (absorb present but weak, directing too early)
- 4 = Strong with clear phase structure and customer focus
- 5 = Exemplary — Absorb → Demonstrate → Lead sequence, customer-first, hidden incentives understood
Dimensions to evaluate:
-
Stakeholder alignment — Does the plan follow the Competence → Credibility → Influence sequence? Does Phase 1 prioritize ABSORBING before directing? Are there concrete customer immersion steps (customer interviews, journey mapping)? Does it show understanding of hidden incentives (what gets your boss/boss's boss fired)? Does it remove "requirements" language in favor of hypotheses?
-
Market & customer intelligence — Does the plan show a week-by-week customer immersion strategy in Days 1-30? Does it map the customer journey before proposing solutions? Does it articulate the organizational power structure and decision-making dynamics? Does it avoid jumping to strategy changes in week 1?
Red flags to check:
- Trying to change strategy in Days 1-14 (skipping absorption)
- No customer interview or journey mapping plan
- No organizational power structure or hidden incentives analysis
- Jumping to "first win" before demonstrating competence
- Language showing "requirements" instead of hypotheses
- No evidence of listening to team feedback first
- Immediate process improvements proposed without context
- Proposing roadmap changes before understanding customer
- No mention of understanding org dynamics or hidden priorities above
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 · 292 lines · 70 tokens per session scan A 59226d1eae6b
First 90 Days Playbook is a skill published in the GitHub repository BrennanJCollins/UnabatedPM-coaching (4 stars, last pushed 22d ago), licensed MIT. It adds 70 tokens to every session and 3,548 once invoked, about $0.0003 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-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.
start-super-pm
Use when starting any product management task - automatically detects task type and invokes appropriate PM skill using intelligent routing.
pm-priority
A Chinese-language procedure for ranking several product requests when time or resources are limited. It supports scoring or grouping methods such as RICE, KANO, and MoSCoW to decide what should be done first.
pm-change
A requirements-change workflow for recording a proposed change, assessing its effects, and deciding whether to approve it.
pm-cross
A Chinese-language planning workflow for coordinating work between departments such as product, engineering, design, testing, operations, and legal.
pm-risk
A structured process for identifying, rating, responding to, and monitoring project risks before important delivery points or launch.