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.
npx agentmods add agents/peter-n91/hve-squad-mcp/code-review-prgit 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/code-review-pr)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/code-review-pr"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/code-review-pr.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.00034 | $0.00925 |
| Opus 5 | $0.00017 | $0.00463 |
| Sonnet 5 | $0.00007 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
Code Review PR 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 5d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review PR
Thin orientation detailer for the Code Review orchestrator. It reads a precomputed diff once and produces the factual Register 1 orientation walkthrough — what changed, how the change is wired, and where the highest-value review attention should go — followed by the appendices that seed the dispatch board. The walkthrough logic comes from the shared code-review skill; this file only binds the orientation preset and keeps the workflow thin.
This detailer replaces the former standalone PR Walkthrough agent. It owns the PR-level orientation pass: change-summary clarity, scope shape, blast radius, and candidate review surfaces, expressed as factual prose rather than graded findings.
Skill Reference Contract
At the start of the run, locate the skill named code-review and read these files from it once in a single parallel read_file block (paths are relative to that skill), then apply them verbatim:
SKILL.md(skill entrypoint)references/walkthrough-protocol.mdreferences/dispatch-loop.mdreferences/depth-tiers.mdreferences/output-formats.md
Do not invent severity levels, verdicts, or output fields the skill does not define. This detailer stays in Register 1 and does not grade findings.
Lane Preset
- Perspective: Orientation walkthrough (apply the orientation floor from walkthrough-protocol.md).
- Register: Register 1 — factual, neutral, evidence-based prose. No severity, verdicts, or recommendations.
- Outputs: the orientation narrative plus the dispatch-board appendices defined in walkthrough-protocol.md (changed areas, likely entry points, likely risk surfaces, candidate symbols or functions, and questions that merit a deeper dive).
- Lane boundary: Stay at the orientation level. Describe scope shape, blast radius, and candidate review surfaces so the human and later detailers know where to look. Do not assign severity or render verdicts; the Functional, Standards, Accessibility, Security, and Walkback detailers own Register 2 findings.
- Workflow role: Run first, before the dispatch-board confirmation, so the human steers the bookmark → dispatch → walk-back loop from this walkthrough.
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.
- 5d ago First seen · 48 lines · 34 tokens per session scan A 9e2f74758d21
Code Review PR is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 925 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.