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/freshworks-developers/fw-dev-toolsWrote 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/freshworks-developers/fw-dev-tools/fdk-react-create)<a href="https://agentmods.dev/commands/freshworks-developers/fw-dev-tools/fdk-react-create"><img src="https://agentmods.dev/badge/commands/freshworks-developers/fw-dev-tools/fdk-react-create/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/freshworks-developers/fw-dev-tools/fdk-react-create"><img src="https://agentmods.dev/badge/commands/freshworks-developers/fw-dev-tools/fdk-react-create.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.00049 | $0.01176 |
| Opus 5.5 | $0.00020 | $0.00470 |
| Sonnet 5.5 | $0.00010 | $0.00235 |
| Haiku 4.5 | $0.00005 | $0.00118 |
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 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.
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
- Follow SKILL.md → Manifest + toolchain gate and Smart prerequisite check.
- Required: Node.js 24.x + FDK 10.x (Meta apps: 10.1.0+ in
engines.fdk). - If
fdkis missing → offerfw-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:
manifest.json"platform-version": "3.0""metaConfig": { "framework": "react", "packageManager": "npm" }"engines": { "node": "24.11.0", "fdk": "10.1.0" }
package.json— React 19+,@freshworks/dew-components,@freshworks/dew-styles,react-router-domapp/index.htmlat app root with#root; add{{{appclient}}}for hybrid/OAuth/SMI- React Router —
<Route path="*" element={<Home />} />plus feature routes under/app/... - DEW sample component — import UI only from
@freshworks/dew-components; styles from@freshworks/dew-styles - No Crayons — no
@freshworks/crayons, no Crayons CDN, no<fw-*>in Meta app README.md— create before validate (see SKILL.md)
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 · 121 lines · 49 tokens per session scan A 63792753ca3a
fdk-react-create is a command published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 23d ago), licensed MIT. It adds 49 tokens to every session and 1,176 once invoked, about $0.0002 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-31.
Other commands, from other repositories
bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.
auto-agent
Automatically route a task to the optimal agent using Q-Learning. There is no auto agent family in v3 — the closest live surface is route, backed by swarm coordinate / autopilot for full multi-agent orchestration.
swarm-init
Initialize a Ruflo swarm with specified topology and configuration.
post-task
Execute post-task cleanup, performance analysis, and memory storage.
session-end
Cleanup and persist session state before ending work.
status
This tool coordinates Claude Code's actions. It does NOT write code or create content.