Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add VandanaAjayDubey111/great-pm/plugin install great-pmWrote 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/commands/vandanaajaydubey111/great-pm/pm-doctor)<a href="https://agentmods.dev/commands/vandanaajaydubey111/great-pm/pm-doctor"><img src="https://agentmods.dev/badge/commands/vandanaajaydubey111/great-pm/pm-doctor/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/commands/vandanaajaydubey111/great-pm/pm-doctor"><img src="https://agentmods.dev/badge/commands/vandanaajaydubey111/great-pm/pm-doctor.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.00041 | $0.00771 |
| Opus 5.5 | $0.00016 | $0.00308 |
| Sonnet 5.5 | $0.00008 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
pm-doctor 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the great-pm /pm-doctor command. Audit great-pm itself — recursively.
What this command checks
great-pm-on-great-pm: the agent roster, the skill library, the hooks, the commands, the memory layers — is it actually wired? Are sessions being logged? Is the audit trail accumulating? Are lessons being captured?
Operating procedure
-
Step 0 — refine the user's query (transparent Mode B). Invoke
query-refiner-pmwith$ARGUMENTS. The refiner returns:You typed: <original> Refined to: <refined brief> What changed: <one line> Proceeding with refined. Reply "use original" to override.Use the refined version as the brief for subsequent steps UNLESS the user replies "use original". Log the refinement to
.great-pm/refinements/$(date +%Y-%m-%d).log. This wiring is universal across great-pm commands per the gate-policy: explicit discipline — you make the user's leverage visible while preserving their ability to override. -
Run the mechanical harness check first. Execute
bash "${CLAUDE_PLUGIN_ROOT:-$HOME/great-pm}/scripts/great-pm-skill-doctor.sh"and include its output — skills-per-agent overload, dangling skill cross-links, and skills missing depth sections (pitfall #5 + the recurring GC pass). This is fast, deterministic, and catches drift the agent audit might miss. -
Invoke
/pm-auditwith scope=great-pmand--read-only(so nothing gets filed as a Beads task — this is diagnostic only). -
pm-auditor will assess great-pm's own setup against the 15-dimension rubric, with the meta lens:
- Discovery → are we listening to OUR great-pm users (you)?
- Strategy → does the design doc still match what's built?
- Specs → do agents have clean, locked patterns?
- Metrics → are verdicts/cost being tracked?
- Governance → are hooks firing? skill-scout running?
- Memory → are lessons accumulating? is
~/.great-pm/decisions.mdgetting populated through/pm-crystallize?
-
Surface the report to the human.
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 · 69 lines · 41 tokens per session scan A e5f5b2b3aa9c
pm-doctor is a command published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 771 once invoked, about $0.0002 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-09-21.
Other commands, from other repositories
CLAUDE
Multi-agent collaboration platform for persistent, proactive AI agents across rooms, workspaces, skills, and external services.
help
Quick reference for all Attune commands.
analyze
Analyze Claude Code transcripts to surface subagent behavior and improvement opportunities.
debate
Expert agents debate to find optimal solutions.
hybrid-manual
Load an existing PRD file and enter review mode. Supports JSON format with stories, priorities, dependencies, and acceptance criteria.
bug-council
Bug Council — spawn 5 diagnostic specialists in parallel to analyze a hard bug from multiple angles, then synthesize a root cause and fix recommendation.