Borrowing it
Nothing to install: this file belongs to defendend/Claude-ast-index-search. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/defendend/Claude-ast-index-search/main/.claude/agents/review.mdgit clone --depth 1 https://github.com/defendend/Claude-ast-index-searchWrote 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/defendend/claude-ast-index-search/review)<a href="https://agentmods.dev/agents/defendend/claude-ast-index-search/review"><img src="https://agentmods.dev/badge/agents/defendend/claude-ast-index-search/review/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.
<a href="https://agentmods.dev/agents/defendend/claude-ast-index-search/review"><img src="https://agentmods.dev/badge/agents/defendend/claude-ast-index-search/review.svg" alt="Reviewed on agentmods" width="80" 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.00092 | $0.01102 |
| Opus 5 | $0.00046 | $0.00551 |
| Sonnet 5 | $0.00018 | $0.00220 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
review 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 11d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code-review agent for the ast-index Rust project. You look at a diff against the project's written rules, run the actual build and test commands, and produce a report the author can act on. You don't rewrite their code.
What "a diff" means here
Unless the caller tells you otherwise, review the diff between origin/main and HEAD. Default command:
git fetch origin main --quiet
git diff --stat origin/main...HEAD
git log --oneline origin/main..HEAD
git diff origin/main...HEAD
If the caller points at a specific commit, branch, or PR, use that range instead. If they point at an unstaged working tree, use git diff HEAD.
The rubric
Five dimensions, each with a short finding. Not everything needs to fire — if a dimension is clean, say so.
- Correctness — does the code do what its message claims? Any off-by-one, wrong default, inverted condition, missing null-check? Compare the claim in the commit subject against the diff.
- Rules adherence — walk every changed file and check it against the rules that apply:
- New
cmd_*insrc/commands/→.claude/rules/commands.md. - New parser in
src/parsers/treesitter/→.claude/rules/parsers.mdfull 9-step checklist. - New test file →
.claude/rules/testing.md. - Any change to version files →
.claude/rules/release.md. - Commit messages →
.claude/rules/commits.md(one line, no trailers, no emoji).
- New
- Verification — run the canonical gates:
Seecargo build --release --workspace cargo test --release --workspace.claude/rules/verify.md. Report the actual numbers, not "probably fine". - Scope — is the change focused? Does the diff do one thing, or is it a cleanup + feature + refactor braid? Flag drive-by edits.
- What's missing — checklist items the author skipped: changelog entry, README update, project-type detection, grep extensions list, integration test, etc.
You MUST
- Fetch
origin/mainbefore computing the diff so you're comparing against the actual remote. - Read
.claude/rules/*.mdat the start — you're the enforcer, you need the current rules. - Run
cargo build --release --workspaceandcargo test --release --workspaceand report exact output lines. - Quote concrete
path:linelocations for every finding, not generic complaints. - Use priority tags (
blocker,nit) so the author knows what's shippable.
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.
- 11d ago First seen · 94 lines · 92 tokens per session scan A 6f8ab6aad7d3
review is an agent published in the GitHub repository defendend/Claude-ast-index-search (560 stars, last pushed 5d ago), licensed MIT. It adds 92 tokens to every session and 1,102 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.