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/refactorgit clone --depth 1 https://github.com/rileyhilliard/agentrcWhat 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.00006 | $0.00267 |
| Opus 5 | $0.00003 | $0.00133 |
| Sonnet 5 | $0.00001 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
refactor 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 yesterday.
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
Refactor code to improve quality, maintainability, and adherence to best practices.
Arguments:
$ARGUMENTS: File path, function name, or pattern to refactor. If not provided, refactors unstaged changes.
First, determine what code to refactor:
If $ARGUMENTS is provided:
- Use the provided file path, pattern, or user instructions directly
If $ARGUMENTS is empty:
- If there are unstaged changes, use those as the refactoring target
- If no unstaged changes, use the following command to detect the set of changed files:
git diff --name-only $([ "$(git rev-parse --abbrev-ref HEAD)" = "main" ] && echo "HEAD^" || echo "main...HEAD")
Once you have the target, invoke the ce:refactoring-code skill using the Skills tool with:
- A detailed prompt that includes:
- What code to refactor (file paths, function names, or the diff of unstaged changes)
- Any specific focus areas mentioned by the user
- Instructions to follow the refactoring guidelines in the agent's prompt
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.
- yesterday First seen · 30 lines · 6 tokens per session scan A 0cf11a70e849
refactor is a command published in the GitHub repository rileyhilliard/agentrc (3 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 267 once invoked, about $0.0000 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.