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-debug)<a href="https://agentmods.dev/commands/bovinphang/frontend-craft/fec-debug"><img src="https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-debug/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/bovinphang/frontend-craft/fec-debug"><img src="https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-debug.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.00035 | $0.00364 |
| Opus 5.5 | $0.00014 | $0.00146 |
| Sonnet 5.5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
fec-debug 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 26d 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-debug-framework to perform front-end problem diagnosis and repair. First classify the problem type (build/runtime/ui/api), and then enter the corresponding diagnosis module to perform the 5-step method (classification → collection → hypothesis → verification → repair). Complex or cross-type issues can be delegated to the fec-debugger subagent.
Question type quick check
| Type | Typical Scenario |
|---|---|
| build | lint/type-check/test/build/CI failed |
| runtime | JS exception, white screen, component rendering error, routing exception, state loss |
| ui | style misalignment, abnormal interaction, animation lag, responsiveness issues |
| api | Request failure, timeout, data inconsistency, CORS, cache issues |
Execution steps
- Read the problems described by users and classify the problem types according to
fec-debug-frameworkStep 1. - Enter the corresponding diagnostic module and perform Step 2 to collect evidence.
- Propose hypotheses based on evidence (Step 3) and verify them one by one (Step 4).
- After confirming the root cause, perform minimal repair (Step 5) and run the affected verification command.
- Output the diagnostic report to
reports/debug-YYYY-MM-DD-HHmmss.md.
##Strong constraints
- Don't "fix" the problem by turning off rules, removing tests, or reducing type safety
- Not easily refactoring irrelevant code
- Don't guess at root cause when evidence is lacking
- It must be verified after repairing, you cannot just change it for accidents
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.
- 26d ago Changed · +35 tokens per session b1d2ebea1320
- 1mo ago First seen · 30 lines · 0 tokens per session scan A b487e5e8ae85
fec-debug is a command published in the GitHub repository bovinphang/frontend-craft (22 stars, last pushed 26d ago), licensed MIT. It adds 35 tokens to every session and 364 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
crystallize
After a session or an incident, turn what happened into reusable knowledge — learn captures this session's lessons, review/approve promotes incident patterns into agent improvements, skill turns a repeating procedure into a skill.
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.
esp-debug
Help debug ESP32 crashes, hangs, and peripheral issues.
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.
analyze-misfires
Identify skills injected where not needed, propose regex and description tightening.
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.