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.
npx agentmods add commands/freshworks-developers/fw-dev-tools/fdk-react-migrategit clone --depth 1 https://github.com/freshworks-developers/fw-dev-toolsWhat 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 | $0.00042 | $0.01462 |
| Opus 5 | $0.00021 | $0.00731 |
| Sonnet 5 | $0.00008 | $0.00292 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade C, and why
fdk-react-migrate scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules coverage .fdk How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FDK React Migrate — Vanilla JS → React Meta
Usage: /fdk-react-migrate
Converts a Platform 3.0 vanilla JS app (Crayons + app/scripts/app.js) to the Meta framework with React + DEW.
Not for Platform 2.x: If platform-version is not "3.0", run /fdk-migrate first, then return to this command.
Step 1: Locate app and verify platform version
- Find
manifest.jsonin the workspace. - If multiple apps → ask user which to migrate.
- Read
platform-version:- Not
"3.0"→ STOP →/fdk-migratefirst. metaConfig.frameworkalready"react"→ inform user; offer/fdk-fixonly.
- Not
Step 2: Prerequisites
Follow SKILL.md toolchain gate: Node 24.x + FDK 10.x (10.1.0+ for Meta).
Step 3: Inventory existing app
Document before changing files:
- Locations and HTML shells (
app/index.html, multi-placeholder names) - Server handlers in
server/server.js— keep all needed SMI/events config/requests.json,oauth_config.json,iparams.json- Frontend logic in
app/scripts/app.js— map to React components
See references/react-meta/js-to-react-migration-checklist.md.
Step 4: Add Meta manifest + package
- Add to
manifest.json:"metaConfig": { "framework": "react", "packageManager": "npm" } - Raise
engines.fdkto10.1.0minimum if lower. - Create/update
package.json:react,react-dom(^19)@freshworks/dew-components,@freshworks/dew-stylesreact-router-dom- Preserve other legitimate deps (axios manifest-pinned, etc.)
Step 5: Restructure frontend
- Keep
app/index.htmlat app root (update to#rootshell; retain{{{appclient}}}if SMI/Data/Request used). - Remove Crayons CDN scripts from HTML.
- Create
app/index.jsxentry importing DEW styles + App component. - Move UI logic from
app/scripts/app.jsintoapp/components/as React components. - Add React Router with
path="*"home route and/app/...feature routes — specific/app/...routes before thepath="*"catch-all. - Remap all navigation paths (CRITICAL — UI breaks if skipped):
- Grep
app/for old paths:href=,window.location,navigate(,<Link to=, click handlers that change views. - Map each vanilla page/view to a React Router route under
/app/...(e.g./demo→/app/demo). - Add a matching
<Route path="/app/...">for every feature page; update everyLink/navigate()to the new path. - Do not leave stale vanilla-only paths —
fdk validatecan pass while the UI stays blank or routes fail.
- Grep
- Multi-location HTML: For each manifest
location.url(e.g.index.html,ticketSidebar.html), ensure the file exists atapp/root (not undercomponents/) with#rootand{{{appclient}}}when SMI/Data/Request is used. - Replace Crayons / plain HTML with DEW components from
@freshworks/dew-components+@freshworks/dew-styles. - Delete or archive
app/scripts/app.jsafter logic is ported (Meta bundles via Vite). - Update icon path in manifest if moving icon to
app/icon.svg.
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.
- 2d ago First seen · 124 lines · 42 tokens per session scan C 2390ed6bb12c
fdk-react-migrate is a command published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 8d ago), licensed MIT. It adds 42 tokens to every session and 1,462 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
github-swarm
Create a specialized swarm for GitHub repository management.
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.
self-healing
Automatically detect and recover from errors without interrupting your flow.
swarm-init
Initialize a Ruflo swarm with specified topology and configuration.
code-review
Automated code review with swarm intelligence.