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/app-templatesgit 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.00000 | $0.02391 |
| Opus 5 | $0.00000 | $0.01196 |
| Sonnet 5 | $0.00000 | $0.00478 |
| Haiku 4.5 | $0.00000 | $0.00239 |
Grade A, and why
app-templates 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform 3.0 App Template Selection
When to use this rule: Creating a new Freshworks Platform 3.0 app.
Template Selection Decision Tree
Step 1: Does the app need a UI?
YES → Go to Step 2
NO → Use Serverless Template (assets/templates/serverless-skeleton/)
Step 2: Did the user explicitly request vanilla JS + Crayons?
YES → Go to Step 3 (vanilla templates) NO → Default: React Meta — Go to Step 4
Step 3: Vanilla JS only (explicit opt-in)
Does the app need backend logic?
YES → OAuth? → oauth-skeleton / else hybrid-skeleton
NO → Use Frontend Template (assets/templates/frontend-skeleton/)
Step 4: React Meta (default for UI apps)
Does the app need backend logic (events, external APIs, data processing)?
YES → Go to Step 5
NO → Use React Meta Frontend (assets/templates/react-meta-frontend-skeleton/)
Step 5: Does the app need OAuth authentication?
YES → Use React Meta OAuth (assets/templates/react-meta-oauth-skeleton/)
NO → Use React Meta Hybrid (assets/templates/react-meta-hybrid-skeleton/)
Template Overview
| Template | Location | Use Case | Key Files |
|---|---|---|---|
| React Meta Frontend (default) | assets/templates/react-meta-frontend-skeleton/ |
UI only, Meta + DEW | app/, metaConfig, package.json, config/iparams.json |
| React Meta Hybrid | assets/templates/react-meta-hybrid-skeleton/ |
UI + Backend + APIs | app/, server/, config/requests.json, metaConfig |
| React Meta OAuth | assets/templates/react-meta-oauth-skeleton/ |
UI + Backend + OAuth | app/, server/, oauth_config.json, metaConfig |
| Frontend (vanilla opt-in) | assets/templates/frontend-skeleton/ |
Crayons vanilla JS | app/scripts/app.js, Crayons CDN |
| Serverless | assets/templates/serverless-skeleton/ |
Backend events, no UI | server/server.js, manifest.json |
| Hybrid (vanilla opt-in) | assets/templates/hybrid-skeleton/ |
Vanilla UI + Backend | app/, server/, config/requests.json |
| OAuth (vanilla opt-in) | assets/templates/oauth-skeleton/ |
Vanilla UI + OAuth | app/, server/, config/oauth_config.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.
- 2d ago First seen · 243 lines · 0 tokens per session scan A aa8744f4b31b
app-templates is a cursor rule published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,391 tokens. 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
startcycle
Autonomous Multi-Agent Development Pipeline (/startcycle).
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.