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.
npx agentmods add agents/seanrreid/rad_framework/quality-reviewergit 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.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.00081 | $0.01486 |
| Opus 5 | $0.00041 | $0.00743 |
| Sonnet 5 | $0.00016 | $0.00297 |
| Haiku 4.5 | $0.00008 | $0.00149 |
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 6d 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 CLAUDE.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 Claude Must Never Do — 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)
Null and undefined safety:
- Dereferencing a value that could be null/undefined without a guard (MEDIUM)
- Optional chaining absent where a null check was clearly intended (LOW)
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.
- 6d 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 2d ago), licensed MIT. It adds 81 tokens to every session and 1,486 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.