fec-init

fec-init is a command for coding agents from bovinphang/frontend-craft. It costs 21 tokens per session (1,909 once invoked), scanned A, original, MIT.

A setup command that installs the frontend-craft project templates and rules for the coding tool used by a project. It detects that tool from existing project files when possible.

In plain words
What is it for?
Use it to initialize frontend-craft for tools such as Codex, Claude Code, Cursor, Windsurf, or other supported runtimes, or to get instructions when automatic setup is not possible.
Why use it?
It removes the need to find the right configuration location and copy templates manually. It also avoids replacing configuration that already exists.

Command

Part of the frontend-craft plugin — 56 skills, 11 commands, 14 agents, 5 hooks, 6 MCP servers shipped together

Install

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.

agentmods
npx agentmods add commands/bovinphang/frontend-craft/fec-init
Clone the repo
git clone --depth 1 https://github.com/bovinphang/frontend-craft

Or install frontend-craft, the plugin that ships this one along with the rest of its 56 skills, 11 commands, 14 agents, 5 hooks, 6 MCP servers.

Wrote 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.

agentmods badge for fec-init

README.md
[![agentmods](https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-init.svg)](https://agentmods.dev/commands/bovinphang/frontend-craft/fec-init)
Your own site
<a href="https://agentmods.dev/commands/bovinphang/frontend-craft/fec-init"><img src="https://agentmods.dev/badge/commands/bovinphang/frontend-craft/fec-init.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,909 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.01909
Opus 5 $0.00010 $0.00955
Sonnet 5 $0.00004 $0.00382
Haiku 4.5 $0.00002 $0.00191

Measured 5d ago against content hash b67b1c71f4b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fec-init 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 5d 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.

commands/fec-init.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Copy the project template provided by frontend-craft to the configuration directory corresponding to the runtime of the current project. Priority will be given to judging the runtime based on the existing configuration in the current directory; if it cannot be judged, it will be selected based on the tool the user is using.

Execution steps

  1. Detect runtime:

    • Existence of .claude/ or Claude Code plug-in environment → claude
    • .codex/ or AGENTS.md exists → codex
    • Existence of .openclaw/, OPENCLAW-CONFIG.md or openclaw.plugin.jsonopenclaw
    • Existence of .qoder/, .qoder/settings.json, .qoder/rules/ or .qoder/skills/qoder
    • exists .cursor/cursor
    • exists .windsurf/windsurf
    • exists .opencode/opencode
    • exists .kilo/kilo
    • exists .gemini/ or GEMINI.mdgemini
    • Exist .github/copilot-instructions.md or .github/instructions/copilot
    • When .trae/, .augment/, .codebuddy/, .clinerules exist, they will be processed according to the corresponding runtime
    • When still unable to determine, ask the user for the runtime currently to be initialized.
  2. Initialize by runtime, do not overwrite existing files without confirmation:

    • claude: Copy Claude templates, hooks, commands, agents, skills and shared rules to .claude/; if .claude/CLAUDE.md already exists, confirm first.
    • codex: Copy templates/codex/AGENTS.md to the project root (if it does not exist), templates/codex/config.toml to .codex/config.toml, shared rules to .codex/rules/; skills/agents should be taken care of by the CLI installation process.
    • openclaw: Copy templates/openclaw/*.md to the project root directory and commands/skills to .openclaw/; if the file already exists, confirm first.
    • qoder: Copy skills to .qoder/skills/, commands to .qoder/commands/, agents to .qoder/agents/, shared rules to .qoder/rules/, hook scripts to .qoder/hooks/, and generate or merge the hooks configuration of .qoder/settings.json.
    • cursor: Copy shared rules to .cursor/rules/*.mdc, retain the fec- skills directory; Note that Cursor does not support hooks of this plug-in.
    • windsurf: Copy commands to .windsurf/workflows/, shared rules to .windsurf/rules/, and skills to .windsurf/skills/.
    • opencode / kilo: Copy commands to .opencode/command/ or .kilo/command/, and skills to the corresponding skills/; OpenCode can complement .opencode/opencode.jsonc.
    • gemini: Copy skills to .gemini/extensions/frontend-craft/skills/. If there is no GEMINI.md, it will be generated by rewriting the Claude template.
    • copilot: merge shared rules into .github/instructions/frontend-craft.instructions.md, commands into .github/prompts/.
    • trae / cline: Write only rules bundles, and make it clear that this is rules-only downgrade mode.
    • antigravity / augment / codebuddy: only install skills; output "This runtime currently has no commands/hooks native adaptation".
  3. Under Claude runtime, copy the following template files from the plug-in's ${FRONTEND_CRAFT_ROOT}/templates/claude/ and ${FRONTEND_CRAFT_ROOT}/templates/shared/rules/ to .claude/ in the project root directory:

    • templates/claude/CLAUDE.md.claude/CLAUDE.md
    • templates/claude/settings.json.claude/settings.json
    • templates/shared/rules/fec-vue.md.claude/rules/fec-vue.md
    • templates/shared/rules/fec-react.md.claude/rules/fec-react.md
    • templates/shared/rules/fec-design-system.md.claude/rules/fec-design-system.md
    • templates/shared/rules/fec-testing.md.claude/rules/fec-testing.md
    • templates/shared/rules/fec-git-conventions.md.claude/rules/fec-git-conventions.md
    • templates/shared/rules/fec-i18n.md.claude/rules/fec-i18n.md
    • templates/shared/rules/fec-performance.md.claude/rules/fec-performance.md
    • templates/shared/rules/fec-source-driven-development.md.claude/rules/fec-source-driven-development.md
    • templates/shared/rules/fec-responsive-design.md.claude/rules/fec-responsive-design.md
    • templates/shared/rules/fec-rendering-patterns.md.claude/rules/fec-rendering-patterns.md
    • templates/shared/rules/fec-api-layer.md.claude/rules/fec-api-layer.md
    • templates/shared/rules/fec-state-management.md.claude/rules/fec-state-management.md- templates/shared/rules/fec-error-handling.md.claude/rules/fec-error-handling.md
    • templates/shared/rules/fec-naming-conventions.md.claude/rules/fec-naming-conventions.md
    • templates/shared/rules/fec-typescript.md.claude/rules/fec-typescript.md
    • templates/shared/rules/fec-code-comments.md.claude/rules/fec-code-comments.md
    • templates/shared/rules/fec-ci-cd.md.claude/rules/fec-ci-cd.md
    • templates/shared/rules/fec-refactoring.md.claude/rules/fec-refactoring.md
    • templates/shared/rules/fec-agent-workflow.md.claude/rules/fec-agent-workflow.md
    • templates/shared/rules/fec-working-modes.md.claude/rules/fec-working-modes.md

Read the full file on GitHub · 69 lines

Changes

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.

  1. 5d ago First seen · 69 lines · 21 tokens per session scan A b67b1c71f4b2

Subscribe to this mod's changes

fec-init is a command published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 1,909 once invoked, about $0.0001 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-08-30.