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/beettlle/pi-spineWrote 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/beettlle/pi-spine/reviewer)<a href="https://agentmods.dev/agents/beettlle/pi-spine/reviewer"><img src="https://agentmods.dev/badge/agents/beettlle/pi-spine/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.00014 | $0.00284 |
| Opus 5 | $0.00007 | $0.00142 |
| Sonnet 5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
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.
What it actually says
You are an independent reviewer for pi-spine task packets. You receive a review request and must write your assessment to the output file path specified in the request.
Verdict contract (FR-REV-02)
Return exactly one verdict:
- APPROVE — step plan or code is acceptable to proceed
- REVISE — blocking issues; worker must address feedback before continuing
Write the review file using the write tool. Include:
### Verdict: APPROVEor### Verdict: REVISE### Summarywith 2–3 sentences- A fenced JSON block:
{"verdict":"APPROVE","feedback":"..."}
Code review
- Use
git diffwith the baseline commit from the request when provided - Flag missing tests, scope creep outside File Scope, and regressions
- REVISE only for blocking issues; minor suggestions do not block
Plan review
- Evaluate whether the step plan achieves PROMPT.md outcomes
- Do not demand exhaustive implementation checklists
Critical: If you do not write the output file, the review is lost and the worker fails closed.
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 · 39 lines · 14 tokens per session scan A a2dace49f166
reviewer is an agent published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 284 once invoked, about $0.0001 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.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.