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 bovinphang/frontend-craft --skill fec-validation-fixgit 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/skills/bovinphang/frontend-craft/fec-validation-fix)<a href="https://agentmods.dev/skills/bovinphang/frontend-craft/fec-validation-fix"><img src="https://agentmods.dev/badge/skills/bovinphang/frontend-craft/fec-validation-fix.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.00079 | $0.00585 |
| Opus 5 | $0.00039 | $0.00293 |
| Sonnet 5 | $0.00016 | $0.00117 |
| Haiku 4.5 | $0.00008 | $0.00059 |
Grade A, and why
fec-validation-fix 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
验证并修复
用途
自动化执行已有验证命令，分析失败原因并安全修复，确保质量门禁达标。
流程
- 从 package.json 或仓库文档中识别可用命令。
- 优先按以下顺序执行：
- lint
- type-check
- unit/integration tests
- build
- 仔细阅读失败输出。
- 将错误按文件、错误类型和依赖关系分组，优先处理阻塞后续诊断的根因。
- 一次只修复一类问题，并显示或记录关键错误上下文。
- 每次关键修复后重新执行受影响命令，确认错误是否减少。
- 如果同一错误连续三次修复仍失败，停止扩大改动并报告阻塞。
- 最后按“预期输出”总结执行结果、修复内容和剩余风险。
失败分诊
- 先修最早出现且会级联的错误，例如缺失类型、导入失败、配置解析失败。
- 区分真实产品 bug、测试环境问题、快照漂移、依赖版本变化和 flaky。
- 对 CI 专属失败记录 Node 版本、包管理器、环境变量、路径大小写和工作目录差异。
- 修复测试时优先修产品代码或测试等待方式，不用删除断言掩盖真实回归。
约束
- 不要盲目关闭规则来消除报错
- 除非有明确理由，不要为了通过检查而降低类型安全
- 不要因为附近测试失败就顺手重写无关模块
- 不要一次性修改多个无关根因
- 不要删除失败测试来让验证通过
- 不要只运行失败命令的片段就声称整体验证通过
详细参考
撰写验证修复报告时，加载 references/report-template.md。
预期输出
- lint / type-check / test / build 等验证命令全部通过
- 失败项已修复或给出明确原因和后续行动
- 修复报告保存为
reports/validation-fix-YYYY-MM-DD-HHmmss.md
What ships with it
1 file 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.
- 4d ago First seen · 52 lines · 79 tokens per session scan A 466aae15b6de
fec-validation-fix is a skill published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 7d ago), licensed MIT. It adds 79 tokens to every session and 585 once invoked, about $0.0004 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 skills, from other repositories
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
fix-bug
Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.
qa
Runtime QA of a change: start the app, test acceptance criteria and edge cases, and report evidence. Use for "test this", "QA", "does it work", exploratory checks, or post-review runtime verification. Not static code review.
debugging-and-recovery
Use when something is broken, a test is failing, behavior is wrong, when investigating a production incident, when a user reports a bug, when a feature works locally but not in another environment, or when the system behaves differently than the contract specifies.
triage-issue
Use when user reports a bug, wants to file an issue, mentions "triage", when investigating a production problem before fixing it, when planning a fix that needs a TDD-shaped GitHub issue, or when a bug needs root-cause analysis before assignment.
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…