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 four-pillars-checkgit 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/four-pillars-check)<a href="https://agentmods.dev/skills/brennanjcollins/unabatedpm-coaching/four-pillars-check"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/four-pillars-check/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/four-pillars-check"><img src="https://agentmods.dev/badge/skills/brennanjcollins/unabatedpm-coaching/four-pillars-check.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.00060 | $0.03323 |
| Opus 5 | $0.00030 | $0.01662 |
| Sonnet 5 | $0.00012 | $0.00665 |
| Haiku 4.5 | $0.00006 | $0.00332 |
Grade A, and why
Four Pillars PM Check 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 — 274 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 the framework interactively. Triggered by direct invocation or natural conversation.
Evaluate mode: Read a document silently, score it against this skill's rubric, 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 document and return a structured assessment. 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 senior PM review
Dimensions to evaluate (all four pillars at high level):
-
Strategy — Does the document clearly articulate WHICH customer/problem is being solved with evidence, or is it vague/missing?
-
Delivery — Is the plan outcome-focused (measure by problem solved) or feature-focused (measure by ships)?
-
Customer Experience — Is the document journey-aware with qualitative insights, or feature-aware/missing CX perspective?
-
Growth — Does it show platform-thinking and business impact, or just feature-thinking?
Apply Four Pillars bias detection to score:
- Identify the dominant pillar (highest coverage — likely matches PM's background)
- Identify the blind spot (lowest coverage — likely neglected area)
- Flag whether this is phase-appropriate (e.g., discovery phase should be Strategy-heavy, not Delivery-heavy)
Return format:
SKILL: Four Pillars Check
CATEGORIES SCORED:
- Strategy: [X]/5
Evidence: "[exact quote showing clear customer/problem or vague assertion]"
Gap: [missing specificity or evidence]
Upgrade: [single highest-leverage change]
- Delivery: [X]/5
Evidence: "[quote showing outcome-focus or feature-focus]"
Gap: [what's missing]
Upgrade: [single highest-leverage change]
- Customer Experience: [X]/5
Evidence: "[quote showing journey/empathy or functional-only thinking]"
Gap: [what's missing]
Upgrade: [single highest-leverage change]
- Growth: [X]/5
Evidence: "[quote showing platform/business impact or feature-thinking]"
Gap: [what's missing]
Upgrade: [single highest-leverage change]
BIAS & BLIND SPOT:
- Dominant pillar: [Strategy/Delivery/CX/Growth] — likely PM background
- Neglected pillar: [the weakest one]
- Phase assessment: [Is this appropriate for the current stage, or over-indexed on wrong pillar?]
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 · 274 lines · 60 tokens per session scan A e6ed188b823f
Four Pillars PM Check is a skill published in the GitHub repository BrennanJCollins/UnabatedPM-coaching (4 stars, last pushed 21d ago), licensed MIT. It adds 60 tokens to every session and 3,323 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.