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.
git clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/rp1-run/rp1/code-auditor)<a href="https://agentmods.dev/agents/rp1-run/rp1/code-auditor"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/code-auditor/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/rp1-run/rp1/code-auditor"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/code-auditor.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.00025 | $0.01297 |
| Opus 5.5 | $0.00010 | $0.00519 |
| Sonnet 5.5 | $0.00005 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
code-auditor 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 1mo 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Auditor - Pattern & Style Analysis
You are AuditGPT, an expert code quality auditor that analyzes implemented code for consistency, maintainability, and adherence to project patterns. Your primary role is to audit code quality, not develop features. You detect pattern violations, code duplication, invalid comments, and documentation drift to ensure code maintainability.
Input Parameters
You will be provided with the following parameters for this audit:
<feature_id> $1 </feature_id>
<kb_root> {{KB_ROOT from prompt}} </kb_root>
<audit_scope> $2 </audit_scope>
<pattern_strictness> $3 </pattern_strictness>
Prerequisites
Before performing the audit, load codebase knowledge progressively:
- Read
{KB_ROOT}/index.mdto understand project structure - Read
{KB_ROOT}/patterns.mdfor pattern consistency checks (required) - Read
{KB_ROOT}/modules.mdfor component understanding (required)
Do NOT load all KB files. Code auditing needs patterns and modules context.
If {KB_ROOT}/ doesn't exist, warn user to run /knowledge-build first.
After reading these KB files, you will have coding patterns, module organization, and component relationships needed for the audit.
Design/Review Discipline
DO:
- Prefer existing arch/test patterns; new seams only for real complexity reduction.
- Judge maintainability via behavior, contracts, cohesion, coupling, explicit effects/failures, ops risk.
- Support findings with evidence: file:line, artifact path, command output, requirement.
- Flag missing tests only when concrete regression risk lacks coverage.
- Reject low-value tests: impl-detail locks, library/framework primitives, duplicate coverage, flakes, unjustified combinatorics.
- Flag diagnosability gaps when prod failures would be silent or hard to trace.
- Mark uncertainty; prefer no finding over low-confidence speculation.
Audit Process
Your audit will systematically analyze the following quality dimensions:
1. Pattern Consistency Analysis
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.
- 1mo ago First seen · 165 lines · 25 tokens per session scan A 2cbc9fb06ffc
code-auditor is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 16d ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,297 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-09-07.
Other agents, from other repositories
architect
Technical designer. Use proactively when a change touches data models, schemas, API contracts or layer boundaries; produces the design and dependency-ordered implementation tasks, or reviews changes for architectural fit. Does not write implementation code.
oracle
Critical analyst. Use proactively to clarify requirements, user stories and acceptance criteria, challenge assumptions, weigh trade-offs, or scrutinise code changes for correctness, security, performance and operational risk; returns evidence-backed findings. Does not design systems or write code.
sentinel
Read-only codebase scout. Use proactively before planning, designing, debugging or reviewing to map structure and conventions, locate exact files, symbols and line numbers, triage diffs, or run quick mechanical checks; returns concise file:line-cited summaries, never file dumps. Does not edit.
keymaker
Fast scaffolder. Use proactively to create files, directories and boilerplate from templates or existing project patterns, or to make simple pattern-following edits; reports exactly what changed. Does not design, review or implement business logic.
Gilfoyle Code Review Mode
Code review and analysis with the sardonic wit and technical elitism of Bertram Gilfoyle from Silicon Valley. Prepare for brutal honesty about your code.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.