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/hamr0/liteagentsWrote 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/hamr0/liteagents/refactor)<a href="https://agentmods.dev/commands/hamr0/liteagents/refactor"><img src="https://agentmods.dev/badge/commands/hamr0/liteagents/refactor/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/commands/hamr0/liteagents/refactor"><img src="https://agentmods.dev/badge/commands/hamr0/liteagents/refactor.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.00007 | $0.03056 |
| Opus 5.5 | $0.00003 | $0.01222 |
| Sonnet 5.5 | $0.00001 | $0.00611 |
| Haiku 4.5 | $0.00001 | $0.00306 |
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 15d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor $ARGUMENTS. A targeted refactor includes the performance pass below — it is on by default, not a separate command.
Guardrails
- Spawn a worker, mid tier stated explicitly (omitted inherits the parent's, not the balanced one; not cheapest/fastest either — judgment degrades there; never a vendor model name). Fall back to running inline if your tool has no subagent mechanism.
- Escalate, never assume. Anything you cannot decide, cannot verify, or that this spec does not cover → stop and report it to the orchestrator (the main session). Never improvise, never widen scope, never fix a side issue you noticed along the way.
- The worker does the work itself — no delegation. The fixer must not spawn subagents of its own. Every edit it reports, and every test run it cites, has to be one it made or ran with its own tool calls: a relayed "I fixed it and the suite is green" from a sub-worker is hearsay, and this command's whole output is the claim that a change landed and the tests still pass. A fix that delegates its work is a report about a report.
- The HITL gates below belong to the orchestrator, not the worker. A subagent cannot hold a conversation with the user, so it cannot run a gate that ends in stop and ask. When one trips — a failing test, a crossed public API boundary, a change bigger than the bullet asked for — the worker stops there and hands the situation back, with the options and its reasoning but no choice made. The orchestrator asks. A worker that picks revert / patch / update-test on the user's behalf has answered a question it was never allowed to ask.
- Edit only what a surviving bullet names. Ledger mode's scope is the bullets that survive revalidation, one change per bullet — not the neighbouring code, not the formatting, not a second finding noticed on the way past. Anything else goes back to the orchestrator to become a new bullet.
- Prove the blast radius with two checks, because neither sees what the
other does.
git status --porcelainat exit must list only files a surviving bullet named — that is this command's scope guarantee, and unlike/branch-reviewit is not expected to be empty. It cannot police the memory directory:.factory/is normally gitignored, so porcelain stays empty whether you deleted a fixed bullet, wrote nothing, or overwroteMEMORY.md. So also hash the files there before you start and again before you report:
and show the comparison: onlyfind .factory/remember -maxdepth 1 -type f -exec md5sum {} + | sort -k2fix-ledger.mdmay differ.last-review.mdin particular is/branch-review's to write — a fixer that touches it forges the gate that judges its own work.
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.
- 15d ago Changed · +12 lines 0caa2311c2e5
- 16d ago Changed · +7 lines 312aac25f0da
- 25d ago Changed · +9 lines 38a573606529
- 28d ago Changed · +31 lines f30e3a408bb3
- 1mo ago Changed · +45 lines · -1 tokens per session b3a912fa5e05
- 1mo ago Changed · +68 lines 800984bb498b
- 1mo ago First seen · 54 lines · 8 tokens per session scan A 554ad426b20f
refactor is a command published in the GitHub repository hamr0/liteagents (25 stars, last pushed 2d ago), licensed Apache-2.0. It adds 7 tokens to every session and 3,056 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
lint
Report drift between FILETREE.md and current repo, read-only. Prompts to run /filetree:update on drift.
find-dead-code
Identify unused code across the codebase.
rclone_listremotes
List all the remotes in the config file and defined in environment variables.
rclone_config_password
Update password in an existing remote.
cleanup
Run a systematic cleanup on the provided code to resolve smells, simplify complexity, and enforce best practices.
rclone_test_changenotify
Log any change notify requests for the remote passed in.