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/react-meta-patternsgit 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.01247 |
| Opus 5 | $0.00000 | $0.00624 |
| Sonnet 5 | $0.00000 | $0.00249 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
react-meta-patterns 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 yesterday.
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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Meta Framework Patterns
Authoritative doc: Create an app with the meta framework
When to use: Any new UI app (default) or vanilla JS → React migration. Vanilla JS + Crayons is opt-in only when the user explicitly requests it.
Default stack
| Layer | Default | Notes |
|---|---|---|
| Framework | Meta (metaConfig.framework: "react") |
In manifest.json, not a separate file |
| UI | @freshworks/dew-components + @freshworks/dew-styles |
Required — see dew-components.md and Storybook |
| React | 19+ preferred | Functional and class components both supported |
| Routing | React Router — path="*" home, /app/... feature routes |
Official Meta sample pattern |
| TypeScript | Optional .tsx / tsconfig.json |
Supported |
Forbidden in Meta workflow
@freshworks/crayons, Crayons CDN,<fw-*>web components- Plain HTML form controls as primary UI (use DEW React components)
metaConfigoutsidemanifest.json
Allowed alongside DEW
Tailwind CSS, PostCSS, MUI, Redux, React Router extras, date-fns, axios (manifest-pinned), and other third-party packages when the user asks or reference patterns apply. Do not remove these during validate/fix unless they break Platform 3.0 rules.
manifest.json (Meta)
{
"platform-version": "3.0",
"modules": { ... },
"metaConfig": {
"framework": "react",
"packageManager": "npm"
},
"engines": { "node": "24.11.0", "fdk": "10.1.0" }
}
metaConfig.framework: required"react"metaConfig.packageManager: optional (npmdefault)- Meta apps: minimum FDK 10.1.0 in
engines.fdk
Directory layout
app/
├── index.html # At app root (name configurable in manifest location.url)
├── icon.svg # Or path declared in manifest
├── index.jsx # Entry (bundled by FDK Vite)
├── components/
├── public/
└── styles/
config/
test/
manifest.json
package.json
vite.config.js # Optional (FDK 10.1.5+)
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.
- yesterday First seen · 125 lines · 0 tokens per session scan A 99088a7ae7de
react-meta-patterns is a cursor rule published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,247 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.