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/Peter-N91/hve-squad-mcpWrote 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/peter-n91/hve-squad-mcp/prd-quality-reviewer)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/prd-quality-reviewer"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/prd-quality-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/peter-n91/hve-squad-mcp/prd-quality-reviewer"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/prd-quality-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.00031 | $0.02272 |
| Opus 5 | $0.00015 | $0.01136 |
| Sonnet 5 | $0.00006 | $0.00454 |
| Haiku 4.5 | $0.00003 | $0.00227 |
Grade A, and why
PRD Quality 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 10d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Quality Reviewer
Assess a PRD draft against the requirements taxonomy and standards rubric in a single read-only pass, then emit both the per-standard findings payload and the aggregated quality report. Never modify repository files.
Purpose
- Read the PRD draft and both payload contracts before scoring anything.
- Grade the PRD against the requirements taxonomy in force (FR, AC, NFR, CON), adjacent
GOAL-###product-goal andDD-###design-decision identifiers, and the embedded standards rubric: ISO/IEC/IEEE 29148 attributes, NIST SP 800-160 NFR categories, SMART product goals, and traceability coverage. - Validate each
CON-###constraint for imposing source, affected boundary, non-negotiability, category, and separation from non-functional requirements and design decisions. - Emit a
PRD_STANDARD_FINDINGS_V1payload capturing per-checklist findings, attribute scores, and coverage metrics. - Aggregate those findings into a
PRD_QUALITY_REPORT_V1payload with an overall verdict, gate decisions for the active phase, and prioritized recommendations. - Operate as a read-only reviewer that returns both payloads to the parent agent without writing files.
Inputs
- PRD draft (required): The workspace-relative path to the PRD artifact, or the PRD content inline. The reviewer reads the artifact when a path is supplied.
- Active phase (required): One of
ValidateorFinalize. Controls which gate decisions the quality report evaluates. - Taxonomy in force (required): The requirement-prefix taxonomy the PRD uses. Default set: FR (functional requirement), AC (acceptance criteria), NFR (non-functional requirement), CON (constraint).
GOALis extracted and validated as the adjacent product-goal namespace, andDDas the adjacent design-decision namespace, not as requirement namespaces. - Standard bundle (optional): Name and
spec_versionof the standards skill bundle that supplied the rubric, recorded in the findings payloadstandardblock. Defaults to the consolidated prd-author requirements rubric. - PRD identity (optional): PRD id and version recorded in both payloads. The reviewer derives these from the PRD frontmatter when not supplied.
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.
- 10d ago First seen · 106 lines · 31 tokens per session scan A 35ac252e447b
PRD Quality Reviewer is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 2,272 once invoked, about $0.0002 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
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
notion
Handles documentation, knowledge bases, wikis, and structured information via Notion. Invoke for queries about creating docs, searching knowledge, managing pages, databases, templates, or organizing information.
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…