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 commands/rileyhilliard/agentrc/reviewgit clone --depth 1 https://github.com/rileyhilliard/agentrcWrote 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/commands/rileyhilliard/agentrc/review)<a href="https://agentmods.dev/commands/rileyhilliard/agentrc/review"><img src="https://agentmods.dev/badge/commands/rileyhilliard/agentrc/review.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 | $0.00010 | $0.00410 |
| Opus 5 | $0.00005 | $0.00205 |
| Sonnet 5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
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 4d 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.
What it actually says
Invoke the ce:code-reviewer agent to perform a comprehensive code review.
If $ARGUMENTS is provided:
- Use the instructions from the user.
If $ARGUMENTS is empty:
Steps:
- Check git status to see if there are uncommitted changes
- Check current branch name
- Determine what to review:
- If uncommitted changes exist: Review uncommitted changes
- If no uncommitted changes exist:
- Check if on a feature branch (not main/master/develop)
- Suggest reviewing all changes in current branch against main (or upstream branch)
- Check the changed files via
git diff --name-only $([ "$(git rev-parse --abbrev-ref HEAD)" = "main" ] && echo "HEAD^" || echo "main...HEAD") - Ask user what should be reviewed
- Invoke the ce:code-reviewer agent with appropriate instructions
Post-Review Workflow
After the code-reviewer agent completes:
-
If APPROVE: Report the review summary. Done.
-
If REQUEST CHANGES:
a. Extract all Critical and Important issues into a checklist:
Review Findings - [branch/scope]: - [ ] [CRITICAL] file.ts:123 - Description - [ ] [IMPORTANT] file.ts:456 - Descriptionb. Ask the user how to proceed using
AskUserQuestion:- "Fix all issues now" (recommended - fix everything the reviewer found)
- "Show the full review, I'll handle it"
c. If fixing: work through the checklist, marking items complete as resolved. After all targeted items are fixed, re-run the code-reviewer agent to verify the fixes don't introduce new issues.
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.
- 4d ago First seen · 48 lines · 10 tokens per session scan A d919a3c6e084
review is a command published in the GitHub repository rileyhilliard/agentrc (3 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 410 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.