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-doc-sync)<a href="https://agentmods.dev/commands/bovinphang/frontend-craft/fec-doc-sync"><img src="https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-doc-sync/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-doc-sync"><img src="https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-doc-sync.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.00030 | $0.00244 |
| Opus 5.5 | $0.00012 | $0.00098 |
| Sonnet 5.5 | $0.00006 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
fec-doc-sync 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 1mo 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-doc-sync to synchronize front-end project documents. Complex multi-language updates can be delegated to fec-doc-updater.
Execution steps
- Read sources of truth:
package.json, lockfile, config,.env.example, routes, API clients/server routes, types/schemas, components, tests, CI, build/deploy config. - Compare README, docs, ADR, changelog, example prompts, setup/deploy/env docs.
- Update stable commands, environment variables, routing/API behavior, component descriptions, deployment steps, version constraints, and migration instructions.
- Keep key information consistent across multi-language documents.
- When the target warehouse itself is a skill/agent/command distribution warehouse, the capability table, metadata, runtime docs and marketplace description are also synchronized.
- Run document consistency, typecheck, test, build or related packaging checks.
Output requirements
Summarize update scope, sources of fact, verification orders and translation risks that still require manual proofreading.
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.
- 1mo ago First seen · 19 lines · 30 tokens per session scan A 9746f96c1cfe
fec-doc-sync is a command published in the GitHub repository bovinphang/frontend-craft (22 stars, last pushed 24d ago), licensed MIT. It adds 30 tokens to every session and 244 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
dotnet-harden
Scan and harden .NET backend code against high-impact anti-patterns such as sync-over-async, lifetime bugs, fat endpoints, and fragile SignalR state.
dotnet-critique
Deep architecture critique of pure .NET backend code. Evaluates AI slop, OOP/SOLID, layer boundaries, DI lifetimes, endpoints, SignalR, data access, concurrency, and distributed-system choices.
py-critique
Deep architecture critique of Python backend code. Evaluates AI slop, SOLID compliance, layer boundaries, anti-patterns, and design quality.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.
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.
document
On-demand documentation generation — API docs, architecture updates, user guides.