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/fw-setup-installgit 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.00054 | $0.04340 |
| Opus 5 | $0.00027 | $0.02170 |
| Sonnet 5 | $0.00011 | $0.00868 |
| Haiku 4.5 | $0.00005 | $0.00434 |
Grade C, and why
fw-setup-install scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.fdk Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
HTTP=$(curl -sS -o /dev/null -w "%{http_code}" -L -I "$FDK_URL" || echo "000") How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FDK setup — install (/fw-setup-install)
/fw-setup install. Supports FDK 10.x (Node 24), FDK 9.x (Node 18, deprecated), and both stacks simultaneously.
Behaviour
| User intent | __FDK_INSTALL_VERSION__ |
FDK tarball | Node |
|---|---|---|---|
/fw-setup-install (no args) |
latest |
https://cdn.freshdev.io/fdk/latest-v24.tgz |
24.11 |
/fw-setup-install 10.1.0 |
10.1.0 |
https://cdn.freshdev.io/fdk/v10.1.0.tgz |
24.11 |
/fw-setup-install --version 10.1.0 |
10.1.0 |
https://cdn.freshdev.io/fdk/v10.1.0.tgz |
24.11 |
/fw-setup-install 9.8.2 |
9.8.2 |
https://cdn.freshdev.io/fdk/v9.8.2.tgz |
18.20 |
/fw-setup-install --version 9.8.2 |
9.8.2 |
https://cdn.freshdev.io/fdk/v9.8.2.tgz |
18.20 |
/fw-setup-install --both |
both |
Both latest-v24.tgz + latest 9.x | 24.11 + 18.20 |
FDK 9.x deprecation: Shows warning and requires user confirmation. Support ends May 31, 2026. See: https://developers.freshworks.com/docs/app-sdk/v3/freshworks-app-sdk/
--both flag: Installs both latest FDK 10.x on Node 24.11 AND latest FDK 9.x on Node 18.20 in one command. Sets nvm alias default 24.11 (FDK 10.x as primary). Idempotent: if both stacks are already verified as installed, report Both stacks already installed — nothing to do. and exit without reinstalling.
Agent pre-step
Parse version from:
- Bare version:
/fw-setup-install 10.1.0or/fw-setup-install 9.8.2 - Flag syntax:
/fw-setup-install --version 10.1.0 - Both stacks:
/fw-setup-install --both - Default (no args):
latest→ FDK 10.x line on Node 24
Replace __FDK_INSTALL_VERSION__ with:
latest— latest FDK 10.x (default)10.x.y— specific FDK 10.x semver (strip leadingv)9.x.y— specific FDK 9.x semver (strip leadingv); SHOW DEPRECATION NOTICEboth— install both latest FDK 10.x on Node 24.11 AND latest FDK 9.x on Node 18.20
Execution
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 · 346 lines · 54 tokens per session scan C bc097e5dc39b
fw-setup-install is a command published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 8d ago), licensed MIT. It adds 54 tokens to every session and 4,340 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). 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.
github-swarm
Create a specialized swarm for GitHub repository management.
self-healing
Automatically detect and recover from errors without interrupting your flow.
swarm-init
Initialize a Ruflo swarm with specified topology and configuration.
post-edit
Execute post-edit processing including formatting, validation, and memory updates.