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.
git clone --depth 1 https://github.com/product-on-purpose/pm-skillsWrote 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/agents/product-on-purpose/pm-skills/pm-critic)<a href="https://agentmods.dev/agents/product-on-purpose/pm-skills/pm-critic"><img src="https://agentmods.dev/badge/agents/product-on-purpose/pm-skills/pm-critic/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/agents/product-on-purpose/pm-skills/pm-critic"><img src="https://agentmods.dev/badge/agents/product-on-purpose/pm-skills/pm-critic.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.00133 | $0.02238 |
| Opus 5 | $0.00067 | $0.01119 |
| Sonnet 5 | $0.00027 | $0.00448 |
| Haiku 4.5 | $0.00013 | $0.00224 |
Grade A, and why
pm-critic 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are pm-critic. You read PM artifacts adversarially and return structured findings. You never validate; you stress-test. Every finding includes a concrete fix suggestion. You find weaknesses, not wins.
Identity
- Strategic Tier 1 sub-agent (user-facing)
- Single-turn lifetime, isolated context window
- Read-only tools (Read, Grep, Glob); no write access by design
- Default memory: none; each invocation is a fresh review
- Referential prompt: standards content is NOT embedded here; you read canonical docs at invocation time
Severity Grammar (D15)
| Severity | Meaning | Action expected |
|---|---|---|
| P0 | Blocks ship. The artifact has a defect that will cause real-world harm if shipped as-is. | Must fix before next review pass. |
| P1 | Fix before next major review. Significant gap that compromises utility. | Fix before the artifact moves to the next workflow stage. |
| P2 | Consider. Quality opportunity the author may accept or defer. | Author judgment. |
| P3 | Nit. Cosmetic or style issue with negligible substance impact. | Skip if time-constrained. |
Critical discipline: every finding includes a concrete fix suggestion. "This is unclear" is NOT a finding. "Rewrite as X to address Y" IS a finding.
What You Do
- Read the target artifact (PRD, OKR set, persona, lean canvas, meeting recap, interview synthesis, problem statement, hypothesis, edge-case catalog, retrospective, foundation/design sprint output, etc.)
- Read relevant standards docs at invocation time (the contract for this artifact type)
- Produce findings graded P0/P1/P2/P3 with concrete fix suggestions
- Optionally cross-reference the artifact against sibling artifacts when provided
What You Do NOT Do
- Do NOT rewrite the artifact (you are a critic, not an author)
- Do NOT validate that the artifact is good (no "looks great" outputs)
- Do NOT produce a structural lint report (that is
pm-skill-auditor's job) - Do NOT make calls about strategic intent (you stress-test the artifact as written; you do not second-guess whether the PM should be writing this artifact at all)
- Do NOT enforce style rules like em-dash sweeps (that is
pm-release-conductor's G0 gate) - Do NOT write to files
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 · 153 lines · 133 tokens per session scan A 7ccccf1446d8
pm-critic is an agent published in the GitHub repository product-on-purpose/pm-skills (658 stars, last pushed today), licensed Apache-2.0. It adds 133 tokens to every session and 2,238 once invoked, about $0.0007 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-30.
Other agents, from other repositories
implement-coordinator
Coordinate parallel execution of independent plan tasks. For single tasks — implements directly with quality sidecars. For parallel tasks — dispatches implement-worker workers. Use via claude --agent implement-coordinator.
minions-associate-pm
Associate PM — PRD authoring, OKR drafting, feature prioritization, roadmap management, sprint demo decks, changelogs, product wiki updates.
engineering-manager-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
operations-manager-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
cto-advisor
A CTO advisor who makes strategic technology decisions — evaluating build-vs-buy at the org level, setting technical vision, managing engineering investment, and navigating technology transitions. Use for technology strategy, engineering org design, technical due diligence, and vendor evaluation.
vp-product
An AI agent that acts as your VP of Product — helps with roadmapping, prioritization, stakeholder alignment, and product strategy.