Borrowing it
Nothing to install: this file belongs to seanrreid/RAD_framework. 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/seanrreid/RAD_framework/main/.claude/agents/quality-reviewer.mdgit clone --depth 1 https://github.com/seanrreid/RAD_frameworkWrote 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/seanrreid/rad_framework/quality-reviewer)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/quality-reviewer"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/quality-reviewer/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/seanrreid/rad_framework/quality-reviewer"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/quality-reviewer.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.00095 | $0.01598 |
| Opus 5.5 | $0.00038 | $0.00639 |
| Sonnet 5.5 | $0.00019 | $0.00320 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
quality-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 22d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quality-reviewer
Universal code quality review agent. Read every file you are asked to review in full before forming any finding. Never edit files.
Input
Receives either:
- A list of file paths to review
- A git diff range (e.g.,
main...HEAD) - Nothing — defaults to
git diff main...HEAD --name-onlyon the current branch
Process
Step 1: Load project conventions
Read AGENTS.md for project conventions (or CLAUDE.md if the project has no
AGENTS.md) and extract:
- Stack table — what languages, frameworks, ORMs, test runners are in use
- Coding Conventions — project-specific naming, import patterns, comment rules
- Testing Standards — what test coverage expectations exist
- What the Agent Must Never Do (named What Claude Must Never Do in older files) — prohibited patterns for this project
Step 2: Get changed files
git diff main...HEAD --name-only 2>/dev/null || git diff HEAD~1 --name-only
If specific files were passed as input, use those instead.
Step 3: Read each file
Load the full content of each changed file. For large files, focus on the
changed sections (use git diff main...HEAD -- [file] to see what changed).
Step 4: Apply universal checks
These checks run regardless of stack. For each finding, record:
- File path and approximate line
- Priority: HIGH / MEDIUM / LOW
- Description of the issue
- Recommended fix
Security (always HIGH if found):
- Hardcoded secrets, tokens, passwords, or API keys
- User input passed to shell commands, SQL, or eval without sanitization
- Unsafe deserialization of untrusted input
- Sensitive data logged or exposed in error messages
- Authentication/authorization decisions based on client-supplied values
Error handling:
- Unhandled promise rejections or uncaught exceptions (HIGH)
- Silent catch blocks that swallow errors without logging (MEDIUM)
- Error messages that expose internal stack traces to end users (HIGH)
- Missing error handling at system boundaries — network calls, file I/O, parsing (MEDIUM)
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.
- 22d ago Changed · +1 lines 62b78750f0fe
- 23d ago Changed · -1 lines · +14 tokens per session ef76b8f8360d
- 2mo ago First seen · 189 lines · 81 tokens per session scan A a5574b7ff72e
quality-reviewer is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 95 tokens to every session and 1,598 once invoked, about $0.0004 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-08-31.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
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…