fdk-react-create

A command that creates a new Freshworks Platform 3.0 app using React Meta, a React-based interface framework, with DEW components and React Router.

In plain words
What is it for?
Use it to scaffold a new React UI app, hybrid app, or OAuth app after confirming the required Node.js and FDK tools are installed.
Why use it?
It gives a new app the expected starting structure and helps route different needs, such as a user interface, backend connection, or OAuth sign-in, to the right template.

Command

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/freshworks-developers/fw-dev-tools/fdk-react-create
Clone the repo
git clone --depth 1 https://github.com/freshworks-developers/fw-dev-tools
Per session 49 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,176 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.00049 $0.01176
Opus 5 $0.00024 $0.00588
Sonnet 5 $0.00010 $0.00235
Haiku 4.5 $0.00005 $0.00118

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

Security

Grade A, and why

fdk-react-create 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 2d 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.

skills/fw-app-dev/commands/fdk-react-create.md · 121 lines

How it starts

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

FDK React Create — React Meta App (Default UI)

Usage: /fdk-react-create

Creates a Platform 3.0 Meta framework app (metaConfig.framework: "react"). This is the default path for any new UI app unless the user explicitly requests vanilla JS + Crayons.

Step 1: Prerequisites

  1. Follow SKILL.mdManifest + toolchain gate and Smart prerequisite check.
  2. Required: Node.js 24.x + FDK 10.x (Meta apps: 10.1.0+ in engines.fdk).
  3. If fdk is missing → offer fw-setup (/fw-setup-install). Do not proceed without CLI.

Step 2: Analyze requirements

Answer (from user request or ask):

Question Routes to
No UI needed? serverless-skeleton — stop this command; use serverless flow
User explicitly asked for vanilla JS / Crayons? /fdk-react-create is wrong — use vanilla frontend-skeleton
Backend / SMI / external API? react-meta-hybrid-skeleton
OAuth? react-meta-oauth-skeleton
UI only? react-meta-frontend-skeleton (default)

Read app-templates.mdc and react-meta-patterns.mdc for product module names (Freshdesk support_ticket, Freshservice service_ticket, etc.).

Step 3: Scaffold the app

Preferred (when CLI available):

cd <parent-directory>
fdk create --template react-starter-template <app-name>
cd <app-name>

Fallback (CLI unavailable or template missing):

cp -r <skill-path>/assets/templates/react-meta-<type>-skeleton/* <app-directory>/

Replace <type> with frontend, hybrid, or oauth.

Step 4: Apply Meta defaults

Ensure the app includes:

  1. manifest.json
    • "platform-version": "3.0"
    • "metaConfig": { "framework": "react", "packageManager": "npm" }
    • "engines": { "node": "24.11.0", "fdk": "10.1.0" }
  2. package.json — React 19+, @freshworks/dew-components, @freshworks/dew-styles, react-router-dom
  3. app/index.html at app root with #root; add {{{appclient}}} for hybrid/OAuth/SMI
  4. React Router<Route path="*" element={<Home />} /> plus feature routes under /app/...
  5. DEW sample component — import UI only from @freshworks/dew-components; styles from @freshworks/dew-styles
  6. No Crayons — no @freshworks/crayons, no Crayons CDN, no <fw-*> in Meta app
  7. README.md — create before validate (see SKILL.md)

Read the full file on GitHub · 121 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. 2d ago First seen · 121 lines · 49 tokens per session scan A 63792753ca3a

Subscribe to this mod's changes

fdk-react-create is a command published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 7d ago), licensed MIT. It adds 49 tokens to every session and 1,176 once invoked, about $0.0002 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-31.