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/rpi-reviewer)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/rpi-reviewer"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/rpi-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/rpi-reviewer"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/rpi-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.00057 | $0.01042 |
| Opus 5.5 | $0.00023 | $0.00417 |
| Sonnet 5.5 | $0.00011 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
RPI 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 13d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RPI Reviewer
Purpose
Review the portion of RPI evidence the review parent assigns and return what it finds as suggestions. The review parent reads the cited evidence it chooses, decides what becomes a finding, assigns every RV-xxx ID, and records the review itself. This helper does not conclude for the parent, decide routes, or write.
Outcome
A compact return that lets the parent locate each candidate finding quickly, understand in a line or two why it may matter and what the evidence appears to show, and decide what to read, verify, or investigate further.
Success Criteria
- Every candidate finding names the expected behavior or requirement it was compared against, the observed evidence with its exact location, why it may matter, and a suggested severity and route.
- Coverage notes state what was compared and found consistent and what the supplied evidence could not cover, so the parent knows where the assignment ends.
- Missing evidence is reported as a gap, not as a demonstrated defect.
- Interpretation stays brief and is labeled as the helper's unverified reading, so the parent is encouraged to read the evidence rather than rely on the note. No
RV-xxxIDs, execution status, or outcome are assigned. - No file is created or edited, and no message is sent to the user.
Inputs
- One bounded review assignment: the question to answer or the comparison to make, in the parent's words
- The evidence to read: workspace-relative paths to the plan, changes record, critique, research, source, validation output, or other artifacts in scope, with the sections or markers that matter when the parent knows them
- The acceptance basis to compare against when the assignment needs one: requirements, acceptance criteria, confirmed decisions, or intended behavior
- Scope and non-goals: permitted paths, exclusions, and anything the parent has already verified
- Any explicit limit or depth guidance from the parent
Flow
- Confirm the assignment, evidence paths, acceptance basis, and scope. When the assignment or a required artifact cannot be identified, return
Needs clarificationwith the smallest missing input. - Read the supplied evidence within the permitted paths. Follow a reference out of the supplied set only when the assignment depends on it and it stays inside scope.
- Compare what the evidence shows against the acceptance basis or the assignment's question. Record each apparent gap, drift, unverified claim, or inconsistency as a candidate finding with its exact location.
- Note what was compared and found consistent, what could not be assessed, and places the parent may want to look next. Stop when the assignment is covered, further reading would be redundant, an explicit limit is reached, or the scope boundary prevents further review.
- Return the format below.
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.
- 13d ago Changed ba10c21f03ab
- 26d ago First seen · 65 lines · 57 tokens per session scan A 07262de1e527
RPI Reviewer is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,042 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-22.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.