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-scaffold)<a href="https://agentmods.dev/commands/bovinphang/frontend-craft/fec-scaffold"><img src="https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-scaffold/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-scaffold"><img src="https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-scaffold.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.00000 | $0.01171 |
| Opus 5 | $0.00000 | $0.00585 |
| Sonnet 5 | $0.00000 | $0.00234 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
fec-scaffold 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create new pages, features or components according to the directory structure agreed upon by the project.
Dependencies and versions
If this scaffolding involves adding or recommending package.json dependencies, follow the "version and dependency" conventions in the project .claude/rules/fec-react.md or .claude/rules/fec-vue.md; if there is no corresponding rule in the project, priority will be given to mainstream stable versions that are compatible with each other (align with official documents, scaffolding default values or package manager recommendations).
Parameter analysis
Parse two arguments from $ARGUMENTS:
- type:
page|feature|component(required) - name: module name, using PascalCase (required)
If a parameter is missing, a usage example is prompted and the user is asked to add:
Usage: /fec-scaffold <type> <Name>
Example:
/fec-scaffold page UserDetail
/fec-scaffold feature payment
/fec-scaffold component DataTable
Execution steps
1. Detection project framework
Check package.json for dependencies:
- Contains
react→ React project - Contains
vue→ Vue project - None → Prompt user to specify manually
2. Detect project conventions and determine target paths
Check src/, app/, pages/, features/, components/, __tests__/, tests/, vitest.config.*, jest.config.*, playwright.config.* and existing component naming. Give priority to reusing existing directories of the project; only use the default path when there is no existing agreement:
- page →
src/pages/<Name>/ - feature →
src/features/<name>/(name is converted to kebab-case) - component →
src/components/<Name>/
If the target directory already exists, the user is prompted to confirm whether to continue.
3. Create directories and files
Depending on the frame and type, create the following structures:
React page
src/pages/<Name>/
├── <Name>Page.tsx
├── components/
│ └── .gitkeep
└── hooks/
└── .gitkeep
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.
- 9d ago First seen · 205 lines · 0 tokens per session scan A 04553c9ddc42
fec-scaffold is a command published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,171 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
audit
Audit an existing codebase. Detects stack, finds gaps, creates tasks, generates PROJECT.md.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
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.
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.
migrate
Migrate existing PROJECT.md to the latest greatcto schema — appends missing fields without touching existing values.
skillify
Capture a repeating pattern as a reusable skill. Run when you notice the same 5+ steps appearing 3+ times across sessions or agents. Produces a skills/ /SKILL.md file.