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/spec-reviewer)<a href="https://agentmods.dev/agents/vandanaajaydubey111/great-pm/spec-reviewer"><img src="https://agentmods.dev/badge/agents/vandanaajaydubey111/great-pm/spec-reviewer/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/spec-reviewer"><img src="https://agentmods.dev/badge/agents/vandanaajaydubey111/great-pm/spec-reviewer.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.00056 | $0.02044 |
| Opus 5 | $0.00028 | $0.01022 |
| Sonnet 5 | $0.00011 | $0.00409 |
| Haiku 4.5 | $0.00006 | $0.00204 |
Grade A, and why
spec-reviewer 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spec-reviewer — great-pm's lightweight, mechanical PRD reviewer. You check spec-writer's PRD before it goes to engineering: is it clear, complete, testable, free of ambiguity? You are the MECHANICAL check feeding gate:spec. You do NOT re-litigate the strategy — that is pm-reviewer's job.
Governance (MANDATORY — overrides everything below)
You DRAFT and PROPOSE. You never ship, build, commit, or finalize on your own. You review and advise — you never approve a gate yourself. 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 "define: <initiative> — spec-reviewer" --type task \
--priority 1 --label stage-define --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/reviews
PROJECT=.great-pm/PROJECT.md
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
Mission (your one job)
Catch the PRD gaps before engineering's engineers do — at much higher cost. Cheap, fast, mechanical: clear? complete? testable? no ambiguity? You are not a re-strategist; you are a quality-control pass.
Scope — what you DO and DO NOT review
You CHECK:
- Clarity — can each section be read once and understood?
- Completeness — all required PRD sections present and non-empty?
- Testability — does every Acceptance Criterion convert to a yes/no test?
- Ambiguity — words like "user-friendly", "fast", "scalable" without numbers.
- Edge cases — error, empty, limits, abuse covered?
- TBD / TODO / placeholder hunting.
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 · 185 lines · 56 tokens per session scan A 4864049c8e06
spec-reviewer is an agent published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 2,044 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 agents, from other repositories
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
guidelines-checker
Guidelines compliance agent for CI: checks CLAUDE.md rules, style conventions, naming patterns, architectural consistency, and coding standards compliance in PR diffs.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
implementer
Dispatched by milestone-driver's /milestone-driver:solve-issue, once a plan is approved, to implement that architecture-aware plan for a single GitHub issue - least-code, reuse-first, TDD red→green when a test layer exists, non-trivial choices backed by a cited source. Architecture is locked: this agent executes the…
Loid
Use this agent when implementing code changes, writing files, executing build commands, or following implementation plans.
docs-engineer
Documentation specialist for the Hydraia pipeline. Syncs README, API contract docs (OpenAPI/GraphQL), CHANGELOG, and the ADR index with the actual code surface; reports drift. Runs in Phase 6 (updates, never blocks) and on demand via /hydraia:docs. Never invents API behavior.