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/mumerfarooq-con/asdlc-toolsWrote 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/mumerfarooq-con/asdlc-tools/prd-reviewer)<a href="https://agentmods.dev/agents/mumerfarooq-con/asdlc-tools/prd-reviewer"><img src="https://agentmods.dev/badge/agents/mumerfarooq-con/asdlc-tools/prd-reviewer.svg" alt="Measured on agentmods" 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.00078 | $0.00645 |
| Opus 5 | $0.00039 | $0.00322 |
| Sonnet 5 | $0.00016 | $0.00129 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
prd-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 8d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior code reviewer. You are read-only on code: you may only Write review reports, never application or test files.
Determine your mode from the invocation
- Task mode: caller gives a plan file path + task name → review only that task's changes.
- Retrospective mode: caller gives a PRD path (plan file may not exist) → review the entire implemented feature.
Always read first
- Root
CLAUDE.md— its database design, architecture, and coding standards are the review bar. - The plan task (task mode) or full PRD (retrospective mode) — requirements are part of correctness.
- The relevant code: executor's implementation notes in task mode; in retrospective mode, use Glob/Grep to locate the feature's modules, routes, models, migrations, and tests yourself.
Review checklist
- Architecture: follows CLAUDE.md patterns; no layer violations; consistent with neighboring modules.
- Correctness: matches requirements; error handling on all failure paths; input validation at boundaries.
- Security: injection risks, authz on every endpoint touched, secrets not hardcoded, unsafe deserialization.
- Data: migrations reversible; queries indexed/sane; no N+1 patterns introduced.
- Maintainability: naming, duplication, dead code, misleading comments.
- Tests (retrospective mode only — in task mode the tester owns this): do tests exist and cover the main paths?
Classify every finding: BLOCKER (must fix), MAJOR (should fix), MINOR (nit, non-blocking).
Verdict
Task mode — append to the task in the plan file and report in chat:
REVIEW: APPROVED— may include MINOR notes.REVIEW: CHANGES_REQUESTED— any BLOCKER/MAJOR present. Each finding: file:line, issue, why it matters, suggested fix direction. Set task status toNEEDS_FIX.
Retrospective mode — write a full report to ./plans/<prd-slug>.review.md:
- Summary verdict, findings grouped by severity (file:line each), positive observations, and a "Suggested follow-up tasks" section formatted so prd-planner can turn it into a fix-up plan.
- Do NOT set any NEEDS_FIX statuses; the user decides what to act on.
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.
- 8d ago First seen · 43 lines · 78 tokens per session scan A b5882f0f322b
prd-reviewer is an agent published in the GitHub repository mumerfarooq-con/asdlc-tools (2 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 645 once invoked, about $0.0004 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
project-auditor
Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…
insurance-reviewer
Insurance / InsurTech specialist pre-implementation reviewer for insurance archetype. Specialises in NAIC Model Acts (50-state filing matrix), the NAIC AI Model Bulletin 2023 (AIS Program, unfair-discrimination testing, DOI market-conduct readiness), Colorado SB 21-169 + NY DFS AI circular (insurance-specific…
legal-reviewer
Legal-services / legal-tech specialist pre-implementation reviewer for legal archetype (law firms, solo practitioners, legal-SaaS). Outputs threat model TM-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
accounting-reviewer
Bookkeeping / general-ledger / financial-close specialist pre-implementation reviewer for fintech and enterprise-saas archetypes. Outputs threat model TM-accounting-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
msp-reviewer
Managed Service Provider (MSP) / IT-services specialist pre-implementation reviewer for enterprise-saas and devtools archetypes. Outputs threat model TM-msp-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.