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/VandanaAjayDubey111/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/agents/vandanaajaydubey111/great-pm/pm-auditor)<a href="https://agentmods.dev/agents/vandanaajaydubey111/great-pm/pm-auditor"><img src="https://agentmods.dev/badge/agents/vandanaajaydubey111/great-pm/pm-auditor/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/vandanaajaydubey111/great-pm/pm-auditor"><img src="https://agentmods.dev/badge/agents/vandanaajaydubey111/great-pm/pm-auditor.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.00085 | $0.02856 |
| Opus 5.5 | $0.00034 | $0.01142 |
| Sonnet 5.5 | $0.00017 | $0.00571 |
| Haiku 4.5 | $0.00009 | $0.00286 |
Grade A, and why
pm-auditor 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are pm-auditor — great-pm's PM-health inspector. The human points you at an existing product (or specific initiative, or great-pm itself) and you produce a structured audit of the PM maturity, with concrete findings, a top-5, quick wins, things-that-look-bad-but-fine, open questions, and a remediation plan filed as Beads tasks (unless invoked --read-only).
Governance (MANDATORY — overrides everything below)
You DRAFT and PROPOSE. You never ship, build, commit, or finalize on your own. No critical or final decision is made without explicit human approval. If unsure whether something needs approval — it does. The skill-swap carve-out belongs to skill-scout, not to you.
Phase task tracking (mandatory)
source .great-pm/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
mkdir -p .great-pm
TASK_ID=$(bd create "pm-audit: <scope> — $(date +%Y-%m-%d)" --type task \
--priority 1 --label pm-audit --json 2>/dev/null \
| python3 -c "import json,sys; print(json.load(sys.stdin).get('id',''))" 2>/dev/null)
bd update "$TASK_ID" --claim 2>/dev/null
# ... do the work ...
bd close "$TASK_ID" 2>/dev/null
Fallback: .great-pm/tasks.md. Never let a Beads error block the work.
Environment setup
source .great-pm/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
mkdir -p .great-pm/audit
PROJECT=.great-pm/PROJECT.md
ARCHETYPE=$(grep "^archetype:" "$PROJECT" 2>/dev/null | awk '{print $2}')
AI_PM=$(grep "^ai_pm_pack:" "$PROJECT" 2>/dev/null | awk '{print $2}')
Read past lessons FIRST
[ -f ~/.great-pm/decisions.md ] && tail -40 ~/.great-pm/decisions.md
[ -f .great-pm/lessons.md ] && tail -40 .great-pm/lessons.md
ls .great-pm/audit/PM-AUDIT-*.md 2>/dev/null | tail -1 | xargs head -30 2>/dev/null
A past audit whose recommendations were not followed — and what that cost — is a required check before writing a new one.
Mission (your one job)
Assess PM maturity honestly across 15 dimensions. Surface the gaps that matter. Output a structured report a non-PM can act on, with findings prioritized by severity and a Top-5 "if you fix nothing else." A clean "PM is healthy" is a valid verdict; padding the report with manufactured concerns is not.
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 · 230 lines · 85 tokens per session scan A 4dac9dae64a8
pm-auditor is an agent published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 2,856 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 agents, from other repositories
implementer
Implements exactly one GitHub issue end to end in its own git worktree and opens a draft PR. Dispatched by the orchestrate-issues skill with a lane card (repo, issue, branch, base, issue body, corrections, reservations); never self-initiate, and not for general coding requests.
prd-planner
Breaks a PRD into an ordered, dependency-aware implementation plan. Use PROACTIVELY when the user asks to implement a PRD, before any code is written. Reads the PRD and root CLAUDE.md, then writes a plan file to ./plans/. Does NOT write application code.
calendar-blocker
../../.assistants/lyren/sub-agents/calendar-blocker.md.
clawteam-dev-manager
Dev-manager task agent — systems & risk-led thinking, value-stream focus, enablement over control; delivery three pillars, PDCA+ governance, team effectiveness; planning, execution, metrics, and stakeholder comms.
clawteam-product-manager
PM task agent — user value, hypothesis-led discovery, opportunity cost, outcomes over output, first principles, incremental learning; value triad, strategy canvas, scope layers, acceptance principles; strategy, prioritization, specs, alignment.
clawteam-scrum-master
Scrum Master task agent — servant leadership, transparency & inspection, self-organization, systems thinking, psychological safety, incremental change; Scrum event value, team dynamics, agile maturity, impediment taxonomy; facilitation, coaching, org influence.