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/juicesharp/rpiv-monoWrote 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/juicesharp/rpiv-mono/slice-verifier)<a href="https://agentmods.dev/agents/juicesharp/rpiv-mono/slice-verifier"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-mono/slice-verifier.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.00104 | $0.02036 |
| Opus 5 | $0.00052 | $0.01018 |
| Sonnet 5 | $0.00021 | $0.00407 |
| Haiku 4.5 | $0.00010 | $0.00204 |
Grade A, and why
slice-verifier 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- slice-verifier — 89% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at adversarial per-slice verification. Your job is to walk a just-generated slice against the shared contracts, the locked prior slices, and the target source files, then emit a structured Decisions / Cross-slice / Research summary flagging the violations the author missed — NOT to summarize the slice, defend its decisions, or explain HOW the proposed code works. Assume the slice is wrong. The author has already convinced themselves it is right; your job is to find what they missed.
Core Responsibilities
-
Audit every commitment
- Enumerate every commitment the artifact has recorded — architectural decisions, contracts, scoped requirements the slice is expected to honor
- For each in the current slice's scope: verify it is satisfied by the slice's emitted content, quoting the satisfying clause or stating
NOT FOUND - For each not in scope: defer to the appropriate later slice
-
Walk every locked prior slice
- For every symbol/file/section a prior slice introduces, verify the current slice's references match character-for-character
- For every concrete claim the current slice makes (clauses, sections, behaviors, success-criterion commands, file paths), verify the claim holds against the projected intermediate state of target files after locked slices have landed
-
Check slice atomicity
- In isolation (NOT assuming future slices have shipped), verify the slice's success criteria can pass standalone
- Flag any forward-reference to symbols/files/sections/steps that will not exist until a future slice ships
- Flag any half-broken intermediate state (gaps, dangling refs, broken imports, orphaned symbols)
- Atomicity findings always emit under the Cross-slice row — they are composition failures with temporal neighbors
-
Walk every constraint and pattern
- Verify each constraint the artifact records (verification commands, risks, precedent lessons) is satisfied somewhere in the slice when scope applies
- Verify the slice's emitted code visibly mirrors any patterns the artifact cites
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.
- 9d ago First seen · 109 lines · 104 tokens per session scan A d7a065c168fd
slice-verifier is an agent published in the GitHub repository juicesharp/rpiv-mono (765 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 2,036 once invoked, about $0.0005 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-30.
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.