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 rules/freshworks-developers/fw-dev-tools/prerequisites-checkgit 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.00020 | $0.00883 |
| Opus 5 | $0.00010 | $0.00441 |
| Sonnet 5 | $0.00004 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
prerequisites-check 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites Check — Mandatory Before Any Task
CRITICAL: Run this check BEFORE generating apps, fixing errors, migrating, refactoring, or reviewing.
Check Commands
node --version # Must output v24.x.x
fdk version # Must output 10.x or newer
Decision Logic
✅ PASS (both conditions met)
- Node version starts with
v24. - FDK version starts with
10.or higher - ACTION: Proceed with user's request
❌ FAIL (either condition fails)
- Node is NOT 24.x
- FDK is NOT 10.x or newer
- Either command fails / not found
- ACTION: STOP immediately, do NOT generate any files, respond with error below
Error Response Template
When prerequisites fail, respond EXACTLY with:
⚠️ PREREQUISITES NOT MET
fw-app-dev requires:
- Node.js 24.x (current: [detected version or "not found"])
- FDK 10.x (current: [detected version or "not found"])
Install prerequisites first:
[if fw-setup skill is available in this workspace:]
1. Run: /fw-setup-install
2. Verify: node --version && fdk version
3. Then retry your command
[if fw-setup skill is NOT available:]
1. Install fw-setup skill:
npx @freshworks/fw-dev-tools install
2. Run: /fw-setup-install
3. Then retry your command
Replace [detected version or "not found"] with actual output from commands.
Examples
Example 1: Node 18 detected
⚠️ PREREQUISITES NOT MET
fw-app-dev requires:
- Node.js 24.x (current: v18.20.8)
- FDK 10.x (current: 9.8.2)
Install prerequisites first:
1. Run: /fw-setup-install
2. Verify: node --version && fdk version
3. Then retry your command
Example 2: FDK not found
⚠️ PREREQUISITES NOT MET
fw-app-dev requires:
- Node.js 24.x (current: v24.11.1)
- FDK 10.x (current: not found)
Install prerequisites first:
1. Run: /fw-setup-install
2. Verify: node --version && fdk version
3. Then retry your command
Example 3: Both missing
⚠️ PREREQUISITES NOT MET
fw-app-dev requires:
- Node.js 24.x (current: not found)
- FDK 10.x (current: not found)
Install prerequisites first:
1. Install fw-setup skill:
npx @freshworks/fw-dev-tools install
2. Run: /fw-setup-install
3. Then retry your command
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 · 127 lines · 20 tokens per session scan A 58bbf0ff9431
prerequisites-check is a cursor rule published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 8d ago), licensed MIT. It adds 20 tokens to every session and 883 once invoked, about $0.0001 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.
Other cursor rules, from other repositories
battle-tested-engineer
Battle-tested engineering judgment for code, refactors, tests, and frontend UI. Ultra-terse caveman style during code work.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.