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/thedecipherist/claude-code-mastery-project-starter-kit/refactorgit clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kitWhat 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.00017 | $0.02281 |
| Opus 5 | $0.00009 | $0.01141 |
| Sonnet 5 | $0.00003 | $0.00456 |
| Haiku 4.5 | $0.00002 | $0.00228 |
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 3d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor — Best Practices Enforcement
Refactor the target file following every rule in this project's CLAUDE.md.
Target: $ARGUMENTS
If --dry-run is passed, report what WOULD change without modifying any files.
Step 0 — Auto-Branch (if on main)
Before making any changes, check the current branch:
git branch --show-current
Default behavior (auto_branch = true in claude-mastery-project.conf):
- If on
mainormaster: automatically create a feature branch and switch to it:
Report: "Created branchgit checkout -b refactor/<filename-without-extension>refactor/<name>— main stays untouched." - If already on a feature branch: proceed
- If not a git repo: skip this check
To disable: Set auto_branch = false in claude-mastery-project.conf. When disabled, warn and ask the user before proceeding on main.
Step 0.5 — Read Before Touching
NEVER refactor blind. Read these files first:
- The target file (fully — every line)
CLAUDE.md— to know the current project rulesproject-docs/ARCHITECTURE.md— to understand where things belong (if it exists)tsconfig.json— to check TypeScript strict mode settings (if it exists)
Also check:
# What imports this file? (understand the blast radius)
# Search for the filename in all source files
Report: "This file is imported by X other files. Changes here affect: [list]"
Step 1 — Audit the File
Run through EVERY check below. For each violation found, note the line number, what's wrong, and what the fix is.
1A. File Size (Rule 7: Quality Gates)
- > 300 lines = MUST split. No exceptions.
- Identify logical sections that can become their own files
- Group by: types, constants, helpers/utilities, main logic, exports
1B. Function Size (Rule 7: Quality Gates)
- > 50 lines = MUST extract. No exceptions.
- Identify functions that do multiple things — each "thing" becomes its own function
- Name extracted functions by what they DO, not where they came from
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.
- 3d ago First seen · 268 lines · 17 tokens per session scan A 5a3da2d4a9ec
refactor is a command published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (337 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 2,281 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-30.
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.