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 skills add FradSer/dotclaude --skill refactor-projectgit clone --depth 1 https://github.com/FradSer/dotclaudeWrote 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/skills/fradser/dotclaude/refactor-project)<a href="https://agentmods.dev/skills/fradser/dotclaude/refactor-project"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/refactor-project/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/skills/fradser/dotclaude/refactor-project"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/refactor-project.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.00057 | $0.00621 |
| Opus 5.5 | $0.00023 | $0.00248 |
| Sonnet 5.5 | $0.00011 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
refactor-project 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 22d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Project Command
Execute automated project-wide refactoring using refactor:code-simplifier agent with cross-file optimization focus.
Pre-operation Checks
Goal: Ensure project-wide execution is explicit and reproducible.
Actions:
- Run
git rev-parse --is-inside-work-tree; if false, inform user that project-wide mode requires a git workspace - Record current revision with
git rev-parse --short HEADand include it in final summary for rollback context - Ignore command arguments and proceed with full-project discovery
Phase 1: Analyze Project Scope
Goal: Discover all code files and display scope summary.
Actions:
- Find all code files using Glob patterns for common extensions
- Filter out
node_modules/,.git/,dist/,build/,vendor/,.venv/ - Group files by language/extension and identify primary source directories
- Display scope summary (file count, languages, directories) then proceed automatically
See references/scope-analysis.md for exclusion patterns and edge cases.
Phase 2: Launch Refactoring Agent
Goal: Execute refactor:code-simplifier agent with project-wide scope and cross-file focus.
Actions:
- Launch
refactor:code-simplifieragent with all discovered code files - Pass cross-file optimization emphasis: duplication reduction, consistent patterns
- Pass aggressive mode flag for legacy code removal
- Agent auto-loads
refactor:best-practicesskill and applies language-specific patterns
See references/agent-configuration.md for detailed Task parameters.
Phase 3: Summary
Goal: Report comprehensive summary of project-wide changes.
Actions:
- Report total files refactored (count and percentage of project)
- List changes categorized by improvement type and cross-file improvements made
- List best practices applied and legacy code removed
- Suggest test suite to run and recommend reviewing changes in logical groups
- Provide safer rollback command tied to recorded baseline (for example:
git restore --worktree --staged .)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 22d ago First seen · 61 lines · 57 tokens per session scan A f9e6ce654384
refactor-project is a skill published in the GitHub repository FradSer/dotclaude (593 stars, last pushed 7d ago), licensed MIT. It adds 57 tokens to every session and 621 once invoked, about $0.0002 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-09-24.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.