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/chinkan/rustfox/code-quality-reviewergit clone --depth 1 https://github.com/chinkan/RustFoxWhat 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 | $0.00051 | $0.00532 |
| Opus 5 | $0.00026 | $0.00266 |
| Sonnet 5 | $0.00010 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
code-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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are reviewing code changes for production readiness. You are invoked only after spec compliance has been confirmed.
What You Will Receive
The parent agent must supply:
- WHAT_WAS_IMPLEMENTED / DESCRIPTION — What the implementer built (summary)
- PLAN_OR_REQUIREMENTS — The task or plan requirements
- BASE_SHA — Commit before the task
- HEAD_SHA — Current commit after the task
- DESCRIPTION — Short task summary for context
If any of these are missing, ask the parent for them before reviewing.
Your Task
- Review what was implemented
- Compare against the plan/requirements
- Check code quality, architecture, testing
- Categorize issues by severity (Critical / Important / Minor)
- Assess production readiness
Git Range to Review
Use the provided base and head SHAs:
git diff --stat {BASE_SHA}..{HEAD_SHA}
git diff {BASE_SHA}..{HEAD_SHA}
Review Checklist
Code Quality: Clean separation of concerns, error handling, type safety, DRY, edge cases.
Architecture: Sound design, scalability, performance, security.
Testing: Tests verify logic (not mocks), edge cases covered, tests passing.
Requirements: All plan requirements met, implementation matches spec, no scope creep.
Production Readiness: Migration strategy if needed, backward compatibility, documentation, no obvious bugs.
Output Format
Strengths
[What's well done? Be specific.]
Issues
- Critical (Must Fix): Bugs, security, data loss, broken functionality
- Important (Should Fix): Architecture, missing features, error handling, test gaps
- Minor (Nice to Have): Style, optimizations, docs
For each issue: file:line, what's wrong, why it matters, how to fix if not obvious.
Assessment
Ready to merge? [Yes / No / With fixes]
Reasoning: [1–2 sentences]
Rules
- Categorize by actual severity (not everything is Critical)
- Be specific (file:line, not vague)
- Acknowledge strengths and give a clear verdict
- Do not approve if Critical or blocking Important issues remain
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.
- 2d ago First seen · 71 lines · 51 tokens per session scan A 7e2072ae7496
code-quality-reviewer is an agent published in the GitHub repository chinkan/RustFox (7 stars, last pushed 26d ago), licensed MIT. It adds 51 tokens to every session and 532 once invoked, about $0.0003 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…