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/airweave-ai/airweave/frontend-rulesgit clone --depth 1 https://github.com/airweave-ai/airweaveWrote 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/airweave-ai/airweave/frontend-rules)<a href="https://agentmods.dev/rules/airweave-ai/airweave/frontend-rules"><img src="https://agentmods.dev/badge/rules/airweave-ai/airweave/frontend-rules.svg" alt="Measured on agentmods" 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.00000 | $0.03221 |
| Opus 5 | $0.00000 | $0.01611 |
| Sonnet 5 | $0.00000 | $0.00644 |
| Haiku 4.5 | $0.00000 | $0.00322 |
Grade A, and why
frontend-rules 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 5d 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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airweave Frontend Architecture & Guidelines
Tech Stack & Core Technologies
- React 18 with TypeScript for type-safe component development
- Vite for fast development builds and HMR
- TailwindCSS with ShadCN UI components for consistent design
- Radix UI primitives with Lucide icons for accessible components
- React Router for client-side routing with file-based organization
- Zustand for state management with persistence
- React Query for server state and data fetching
- Auth0 for authentication with custom context wrapper
- SSE (Server-Sent Events) for real-time sync progress
Project Structure
frontend/src/
├── components/ # Reusable UI components
│ ├── ui/ # ShadCN UI primitives
│ ├── shared/ # Shared business components
│ └── [feature]/ # Feature-specific components
├── pages/ # Route-level components
├── lib/ # Core utilities and providers
│ ├── api.ts # API client with auth integration
│ ├── stores/ # Zustand state stores
│ └── auth-context.tsx # Auth provider
├── hooks/ # Custom React hooks
├── services/ # Business logic services
├── config/ # Configuration files
├── constants/ # App constants
└── styles/ # Global CSS styles
└── toast.css # Custom toast styling
API Layer (lib/api.ts)
The API client is the central hub for all backend communication with sophisticated features:
Core Features
- Token Management: Automatic token injection via provider pattern
- Request Queuing: Queues requests while auth initializes
- Organization Context: Auto-injects
X-Organization-IDheader - Session Tracking: Auto-injects
X-Airweave-Session-IDheader with PostHog session ID for session replay linking - Auto-Retry: Refreshes token on 401/403 and retries
- Organization Auto-Switching: Detects resource org mismatches and switches context
- Type-Safe Responses: Returns typed Response objects
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.
- 5d ago First seen · 395 lines · 3,221 tokens per session scan A db0e64e4e373
frontend-rules is a cursor rule published in the GitHub repository airweave-ai/airweave (6,566 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,221 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-30.
Other cursor rules, from other repositories
frontend-development
Most coagents examples have a ui/ folder with Next.js applications.
examples-and-demos
Multi-agent systems with complex workflows.
suggestions-development
When working with suggesitons, always load this up.
agent-development
Python agents are typically in folders named agent-py/ or agent/ and use the sdk-python/ package.
quick-reference
Cursor rule "quick-reference" from CopilotKit/CopilotKit, covering copilotkit quick reference, need to...?, build a simple copilot, create multi-agent systems and integrate with crewai.
development-workflow
CopilotKit uses a monorepo structure with.