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/rules/freshworks-developers/fw-dev-tools/preflight)<a href="https://agentmods.dev/rules/freshworks-developers/fw-dev-tools/preflight"><img src="https://agentmods.dev/badge/rules/freshworks-developers/fw-dev-tools/preflight/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/rules/freshworks-developers/fw-dev-tools/preflight"><img src="https://agentmods.dev/badge/rules/freshworks-developers/fw-dev-tools/preflight.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.00021 | $0.00348 |
| Opus 5.5 | $0.00008 | $0.00139 |
| Sonnet 5.5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
preflight 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.
What it actually says
Preflight (orchestration)
Run on first message of an IDE session or when opening an app workspace. Full prose: Tier 2 agent-behaviour.md §preflight.
Executable checks
- Session —
bash ~/.fw-dev-tools/scripts/session-read.sh <app-dir>(or treat missing file as fresh). - Toolchain —
node -v(expect v24.x),fdk --version(expect 10.x). If missing → dispatch fw-setup via controller; do not validate until pass. - Manifest — confirm
manifest.jsonin active app dir when intent is notcreate-new. - Publish token — before fw-publish chain, smoke-test MCP auth (
list_custom_appsper fw-publish playbook).
Resume rules
- Show resume banner when valid session exists.
- Stale (
updated_at> 30 days): require explicit confirm. - Corrupt JSON: offer
session-reset.sh <app-dir> --force. - Never auto-publish on resume.
Session scripts
| Script | Purpose |
|---|---|
session-read.sh |
Read .fw-session.json |
session-write.sh |
Merge milestone / phase updates |
session-reset.sh |
Delete session (--force) |
Schema: ~/.fw-dev-tools/specs/fw-session.schema.json or skills/shared/references/fw-session-schema.json.
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 · 34 lines · 21 tokens per session scan A 8b8e4f98e777
preflight is a cursor rule published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 23d ago), licensed MIT. It adds 21 tokens to every session and 348 once invoked, about $0.0001 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-09-09.
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.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.