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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/dev-refactor)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/dev-refactor"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/dev-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/christopherlouet/claude-base/dev-refactor"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/dev-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.00000 | $0.00376 |
| Opus 5.5 | $0.00000 | $0.00150 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
dev-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 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.
What it actually says
Agent DEV-REFACTOR
Code refactoring with behavior preservation and quality improvement.
Request context
$ARGUMENTS
Objective
Improve the structure, readability and maintainability of the code WITHOUT changing its external behavior. Atomic commits at each transformation.
Workflow
- Prepare: Run tests, check coverage (>80% = safe, 60-80% = add tests, <60% = tests first)
- Analyze: Identify code smells (Long Method, Large Class, Duplicate Code, Deep Nesting, Magic Numbers, Feature Envy, etc.)
- Plan: List transformations by priority and risk
- Execute: For each transformation: apply ONE transformation, run tests, if OK commit, if KO revert
- Validate: Final tests, coverage >= initial, lint and typecheck OK
Main techniques
- Extract Method, Extract Class
- Replace Conditional with Polymorphism
- Introduce Parameter Object
- Replace Magic Numbers with Constants
- Simplify Conditionals (early returns)
Expected output
Initial analysis (code smells, coverage), ordered transformation plan, transformations performed with atomic commits, result (tests, coverage, complexity).
Related agents
| Agent | When to use it |
|---|---|
/work:work-explore |
Understand the code before refactoring |
/dev:dev-tdd |
Add missing tests |
/qa:qa-review |
Post-refactoring review |
/work:work-commit |
Atomic commits |
IMPORTANT: External behavior MUST NOT change.
IMPORTANT: Small steps. One change at a time. Test after each change.
YOU MUST have sufficient test coverage BEFORE refactoring.
NEVER refactor and add features at the same time.
Think hard about the order of transformations to minimize risks.
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 · 54 lines · 0 tokens per session scan A 5c17f9994113
dev-refactor is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 376 tokens. 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-03.
Other commands, from other repositories
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
deploy
Deploy application with pre/post-deploy checks.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
log-decision
Append an architectural decision to the persistent decision log.
session-log
Explain where session history lives now that the toolkit keeps no session log.