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-debuggit 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.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.00000 | $0.00363 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $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 4d 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.
- 4d 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 (21 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 363 tokens. 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
import
Import a shared context bundle, or take a teammate's newer copy of one you already have.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
extensions
Show what the connected context expects to reach, and whether this machine provides it.
list
List the NeatContext contexts you can connect.
build
Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.