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 skills add freshworks-developers/fw-dev-tools --skill fw-setupgit 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/skills/freshworks-developers/fw-dev-tools/fw-setup)<a href="https://agentmods.dev/skills/freshworks-developers/fw-dev-tools/fw-setup"><img src="https://agentmods.dev/badge/skills/freshworks-developers/fw-dev-tools/fw-setup/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/skills/freshworks-developers/fw-dev-tools/fw-setup"><img src="https://agentmods.dev/badge/skills/freshworks-developers/fw-dev-tools/fw-setup.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.00160 | $0.07203 |
| Opus 5.5 | $0.00064 | $0.02881 |
| Sonnet 5.5 | $0.00032 | $0.01441 |
| Haiku 4.5 | $0.00016 | $0.00720 |
Grade D, and why
fw-setup scanned grade D with 4 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Use nvm ALWAYS** - NEVER install Node globally, NEVER use `sudo npm` Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
**Post-install MCP (optional):** After successful install/upgrade only — offer Marketplace MCP setup; **Cursor** config shape: [`references/templates/cursor-mcp-config.json`](references/templates/cursor-mcp-config.json); Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| `~/.fdk` persists after uninstall | MEDIUM | Manual removal: `rm -rf ~/.fdk` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Pinned 10.x.y / 9.x.y:** CDN `https://cdn.freshdev.io/fdk/vX.Y.Z.tgz` (verify **HTTP 200** with `curl` before `npm install -g`). How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Entry contract
- Invoked by: controller when toolchain missing or user requests FDK/Node setup
- Preconditions: User consent for mutating install/upgrade/downgrade operations
- Returns:
done(fdk + node verified globally) |blocked(user declined install) |escalate(verification failed after retries) - On complete: hand control back to the controller — controller resumes prior intent chain (e.g. fw-app-dev)
- Session:
session-read.shat start; on success —session-write.sh <app-dir> progress.phase=setupwhen app dir present
FDK Setup
MOST IMPORTANT - ZERO TOLERANCE: FDK installation is NEVER complete until verification shows FDK accessible globally AND persists across new shells. NEVER say "installation complete" with ANY verification failures.
MANDATORY ENFORCEMENT: Verify every mutating operation (install, upgrade, downgrade, uninstall, and /fw-setup-troubleshoot --fix) with actual shell tests. /fw-setup-status, /fw-setup-troubleshoot (no --fix), and /fw-setup-use are non-Task flows (/fw-setup-use may only add .nvmrc when the user asked for --write-nvmrc). Keep iterating until verification passes. No exceptions.
You are a Freshworks FDK installation and version management enforcement layer.
Progressive disclosure: Canonical FDK / Node / Platform pins live in docs/engine-matrix.md (single source of truth—load when version truth is disputed). For per-project Node / FDK stack switching, use commands/fw-setup-use.md first, then references/macos.md / references/cross-scenarios.md for .nvmrc patterns. For complex multi-Node scenarios, PATH conflicts, or OS-specific installation issues, load references/cross-scenarios.md. For macOS-specific issues, load references/macos.md. For Windows-specific issues, load references/windows.md (PowerShell 5.1 &&, where vs where.exe, PATH refresh after nvm use). For fdk: command not found errors, load references/error-command-not-found.md. For interactive manual troubleshooting when automated --fix fails, load references/interactive-troubleshooting-guide.md and follow the step-by-step SOP protocol (ONE command at a time, wait for human output, adapt based on results). For non-blocking local fdk run, execute scripts/fw-setup-run-background.sh from the app root (shell script, not a slash command); use scripts/fw-setup-stop-shell-tasks.sh to signal matching fdk run / fdk tunnel processes.
What ships with it
30 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .claude-plugin/plugin.json 634 B
- .cursor-plugin/plugin.json 2.6 KB
- commands/fw-setup-downgrade.md 22 KB
- commands/fw-setup-install.md 13 KB
- commands/fw-setup-status.md 3.2 KB
- commands/fw-setup-troubleshoot.md 11 KB
- commands/fw-setup-uninstall.md 11 KB
- commands/fw-setup-upgrade.md 5.1 KB
- commands/fw-setup-use.md 13 KB
- README.md 14 KB
- references/cross-platform-scenarios.md 8.4 KB
- references/cross-scenarios.md 23 KB
- references/error-command-not-found.md 6.3 KB
- references/interactive-troubleshooting-guide.md 11 KB
- references/macos.md 4.0 KB
- references/node-version-sop.md 7.8 KB
- references/npm-permissions-sop.md 2.1 KB
- references/nvm-install-sop.md 5.3 KB
- references/real-world-scenarios.md 12 KB
- references/shell-persistence-sop.md 8.1 KB
- references/templates/cursor-mcp-config.json 166 B
- references/templates/fdk9-deprecation-warning.txt 267 B
- references/version-policy.md 2.1 KB
- references/windows.md 16 KB
- rules/fdk-enforcement.mdc 2.6 KB
- scripts/detect-install-method.sh 1.0 KB runs code
- scripts/fw-setup-quick-detect.sh 380 B runs code
- scripts/fw-setup-run-background.sh 774 B runs code
- scripts/fw-setup-stop-shell-tasks.sh 2.1 KB runs code
- scripts/fw-setup-use.ps1 9.6 KB runs code
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 Changed · +8 lines 415ddc472221
- 1mo ago Changed · +1 lines 2bc0b73097e5
- 1mo ago First seen · 372 lines · 160 tokens per session scan D 7ee3d273ded2
fw-setup is a skill published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 1mo ago), licensed MIT. It adds 160 tokens to every session and 7,203 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it D with 4 findings (asks for root, reads mcp configuration, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
battle-tested-engineer
Engineering judgment for code write/refactor/test and frontend UI. Trigger on code review, legacy cleanup, tests, UI with data, bloat/over-engineer complaints — even with no explicit mention, before any diff/rewrite/test suite. Output ultra-terse caveman style; code, commits, PR desc, security warnings stay normal…
skillsmith-agent
Delegate your agent-skill lifecycle: keep skills current, audit and clean up your inventory, and vet skills before you install them. The Skillsmith Agent diagnoses in full for free, proposes a batched fix plan, and changes files only with your per-changeset approval, with one-step undo. Triggers: "ask the Skillsmith…
skillsmith
Discover, install, compare, and manage Claude Code skills. Search the registry, get recommendations, validate skill quality, and manage your installed skills.
agent-checkpointing
Implement checkpointing for agent recovery, debugging, and replay. Use this skill when building recoverable agents, implementing replay, debugging agent failures, or creating resumable workflows. Activate when: agent checkpoint, agent recovery, resume agent, agent restart, workflow replay, agent debugging, failure…
durable-state-patterns
Implement persistent agent state that survives failures and restarts. Use this skill when building stateful agents, implementing checkpointing, persisting agent memory across sessions, or recovering from failures. Activate when: durable state, agent persistence, checkpointing, agent recovery, stateful agents, state…
agent-memory-systems
Use this skill when implementing memory for AI agents. Activate when the user needs agents to remember past interactions, implement context persistence, build knowledge bases for agents, design agent state management, or create shared memory between multiple agents.