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/bovinphang/frontend-craft/fec-refactorgit 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)<a href="https://agentmods.dev/commands/bovinphang/frontend-craft/fec-refactor"><img src="https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-refactor.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 | $0.00024 | $0.00249 |
| Opus 5 | $0.00012 | $0.00125 |
| Sonnet 5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
fec-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 yesterday.
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
Execute a pure structural refactoring under a recorded behavior contract.
Workflow
- Classify the request and redirect feature work, unknown bugs, migrations, dead-code cleanup, or general review when they own the task.
- Discover project facts and establish the existing validation baseline.
- If no plan is supplied, diagnose evidence and build an ordered plan first. If a plan is supplied, revalidate it against the current code.
- Record risk and Diff Budget.
DANGERstops for explicit approval unless the specific compatibility plan is already authorized. - Execute one refactoring step with one primary structural intent.
- Immediately run the narrowest sufficient verification and inspect actual scope.
- If the step causes a new regression, revert that step before attempting a smaller or different transformation.
- Repeat only after the current step is green and within budget.
- Run final broad validation and save
reports/refactoring/refactoring-YYYY-MM-DD-HHmmss.mdwith aPASS,PARTIAL, orNOT PROVENbehavior-preservation verdict.
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.
- yesterday First seen · 19 lines · 24 tokens per session scan A ad4fbf6e17dd
fec-refactor is a command published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 249 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-09-03.
Other commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
coding-audit
Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
update-workflow
Regenerate an existing custom workflow's shortcut command wiring from the current swarm template.
import
Import a shared context bundle, or take a teammate's newer copy of one you already have.