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/bovinphang/frontend-craftWrote 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/bovinphang/frontend-craft/fec-refactor-clean)<a href="https://agentmods.dev/commands/bovinphang/frontend-craft/fec-refactor-clean"><img src="https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-refactor-clean.svg" alt="Measured on agentmods" 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.00027 | $0.00176 |
| Opus 5 | $0.00014 | $0.00088 |
| Sonnet 5 | $0.00005 | $0.00035 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
fec-refactor-clean 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 7d 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
Press fec-refactor-clean to perform a safe clean. Complex cleanup can be delegated to fec-refactor-cleaner.
Execution steps
- Establish the current verification baseline.
- Use existing tools in the warehouse or
rgto collect unused candidates. - Check dynamic references, routing, barrel export, Storybook, test and style entry.
- Divide the candidates into SAFE, CAUTION, and DANGER.
- Only clean SAFE items; other items output suggestions and evidence.
- Rerun the affected verification commands after each batch cleanup.
Output requirements
Save the clean report to reports/refactor-clean-YYYY-MM-DD-HHmmss.md.
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.
- 7d ago First seen · 19 lines · 27 tokens per session scan A abf973d3cefb
fec-refactor-clean is a command published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 176 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
review
12-angle code review + skeptical triage (3-round + arbiter) for security/reliability P0/P1 findings, OR traceability tree. Default: review current branch vs main. --deep: triage ALL P0/P1 angles (not just security). With trace : render REQ → IMPL → TEST tree for impact analysis. Creates or closes gate:code for…
audit
Audit an existing codebase. Detects stack, finds gaps, creates tasks, generates PROJECT.md.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
resume
Resume a previous session. Reads recent session logs, open tasks, and last decisions — gives Claude full context without re-explaining the project.
close-review
Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with double-entry integrity, ASC 606 revenue-recognition, period-lock, and SOX ITGC gaps.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.