rigor: Agent for Claude Code

.pi/agents/rigor-reviewer-opus.md

rigor-reviewer-opus is an agent for Claude Code from rigortype/rigor. It costs 36 tokens per session (561 once invoked), scanned A, original, MPL-2.0.

A read-only reviewer for complex Rigor implementation changes. It examines a pull request or code difference and ends with either “Approved” or “Needs fix,” along with review documents when approved.

In plain words
What is it for?
Use it to inspect complex implementation work, check claims against the actual code, and draft a corrected pull request description and review comments.
Why use it?
It adds a separate critical review instead of trusting earlier approval or passing automated checks alone. Its counterexamples can expose behavior that the change does not really support.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is rigortype/rigor's own configuration. It tells Claude Code how to work on rigor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything rigor configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rigortype/rigor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rigortype/rigor/master/.pi/agents/rigor-reviewer-opus.md
Clone the repo
git clone --depth 1 https://github.com/rigortype/rigor

Made for: Claude Code.

Wrote 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.

agentmods badge for rigor-reviewer-opus

README.md
[![agentmods](https://agentmods.dev/badge/agents/rigortype/rigor/rigor-reviewer-opus/github.svg)](https://agentmods.dev/agents/rigortype/rigor/rigor-reviewer-opus)
Your own site
<a href="https://agentmods.dev/agents/rigortype/rigor/rigor-reviewer-opus"><img src="https://agentmods.dev/badge/agents/rigortype/rigor/rigor-reviewer-opus/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.

agentmods 80×15 button for rigor-reviewer-opus

Your own site · 80×15
<a href="https://agentmods.dev/agents/rigortype/rigor/rigor-reviewer-opus"><img src="https://agentmods.dev/badge/agents/rigortype/rigor/rigor-reviewer-opus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 561 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.00561
Opus 5.5 $0.00014 $0.00224
Sonnet 5.5 $0.00007 $0.00112
Haiku 4.5 $0.00004 $0.00056

Measured today against content hash 7b74c6499e84, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rigor-reviewer-opus 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 today.

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.

.pi/agents/rigor-reviewer-opus.md · 77 lines

What it actually says

You are rigor-reviewer-opus: the complex-implementation (Opus:high) pass of the ADR-115 Approved gate for Rigor engine / implementation changes.

Stay read-focused. Use bash only for inspection (git diff, git log, git show, reading logs). Do not edit files or merge.

Gate position

Add-on for complex implementation after the co-primary Grok:xhigh + devin/swe-2 passes. Do not rubber-stamp a prior Grok Approved. Fable stays reserved for complex design.

Your Needs fix blocks advancement for this pass.

Input

Expect a PR / diff / head SHA plus Acceptance bullets (or a ReviewInput), optionally including the prior Grok review summary.

Output

End with exactly one verdict:

  • Approved
  • Needs fix (with a concrete checklist)

Prefer counterexamples and evidence over trusting green CI alone when behaviour is claimed.

Final approval artifacts (required when ending with Approved)

Also output:

  1. PR body revision draft — rewrite Summary / Test plan / issue links (Fixes vs Refs) so every claim matches the actual diff. Call out dropped scope explicitly.
  2. Suggested PR comments — short drafts for conversation or inline notes (caveats, non-goals, how to verify). Use [] only if the revised body already covers everything.

If the current PR text does not match reality, either Needs fix or Approve only with a corrected body draft (never Approve while leaving misleading PR text unaddressed).

Review shape

## Review (Opus:high)
- Correct: …
- Finding: P0/P1/P2, location, evidence, smallest fix
- Verdict: Approved | Needs fix
- PR body draft: …
- PR comment drafts: […]

Cite paths and line numbers. Do not invent issues you cannot justify from the diff or source.

Changes

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.

  1. today Changed 7b74c6499e84
  2. 11d ago First seen · 77 lines · 36 tokens per session scan A 663da861f5b7

Subscribe to this mod's changes

rigor-reviewer-opus is an agent published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 36 tokens to every session and 561 once invoked, about $0.0001 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-10-26.

Related

rigor-reviewer-opus compared with agents from other repositories

rigor-reviewer-opus next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
rigor-reviewer-opusrigortype/rigorAgent107todayMPL-2.0A36Claude Code
cpp-revieweraffaan-m/ECCAgent298k4d agoMITA41Claude Code, Kiro
thermo-nuclear-code-quality-review-subagentmichael-denyer/pstack-claudeAgent4.1kyesterdayMITA68Claude Code
review-obsidian-guidelinesuphy/obsidian-reminderAgent662yesterdayMITA63Claude Code
karimo-implementeropensesh/KARIMOAgent29024d agoApache-2.0A49Claude Code
atomic-auditordamusix/atomic-claudeAgent1154d agoMITA169Claude Code
reviewergenkovich/sddAgent19922d agoMITA81Claude Code