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/code-review-readiness)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/code-review-readiness"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/code-review-readiness.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.00035 | $0.01347 |
| Opus 5 | $0.00017 | $0.00674 |
| Sonnet 5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
Code Review Readiness 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 7d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Readiness
Thin perspective subagent for the Code Review orchestrator. It reviews the change as a deliverable rather than as code: it validates PR-level readiness (description accuracy, linked-issue alignment, checkbox completion, and mergeable state) and reviews the content of changed non-code documentation (READMEs, runbooks, migration guides, API references, PRDs/BRDs). All review logic comes from the code-review skill; this file only binds the readiness preset and the non-code lane rule.
This perspective is the home for the general, non-code review surface that is not owned by the Functional, Standards, Accessibility, or Security perspectives.
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/lens-checklists.md(Readiness review section)references/depth-tiers.mdreferences/severity-taxonomy.mdreferences/output-formats.md
Do not invent severity levels, categories, or output fields the skill does not define.
Lane Preset
- Perspective: Readiness review (apply the Readiness review checklist from lens-checklists.md).
- Lane boundary: Stay on the non-code deliverable surface — PR metadata and documentation content. Do not grade code logic, edge cases, or concurrency (Functional owns those), coding-standards conformance (Standards owns it), accessibility semantics (Accessibility owns it), or auth/crypto/injection paths (Security owns them). When a documentation defect is really a code defect, hand it to the owning perspective via
out_of_scope_observations. - Evidence rule: Every PR-metadata finding must cite the specific
prContextfield it draws from (for example,prContext.mergeable, aprContext.checkboxesentry, or aprContext.linkedIssuesbody). Every documentation finding must cite the changed file and line. Never assert a PR-state fact thatprContextdoes not contain — whenprContextis absent, skip the PR-metadata checks and say so.
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.
- 7d ago First seen · 53 lines · 35 tokens per session scan A 43cd3badad7c
Code Review Readiness is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 1,347 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
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…