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/backend-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/backend-rules)<a href="https://agentmods.dev/rules/airweave-ai/airweave/backend-rules"><img src="https://agentmods.dev/badge/rules/airweave-ai/airweave/backend-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 | $0.00000 | $0.01458 |
| Opus 5 | $0.00000 | $0.00729 |
| Sonnet 5 | $0.00000 | $0.00292 |
| Haiku 4.5 | $0.00000 | $0.00146 |
Grade A, and why
backend-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 4d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airweave Backend Architecture
Core Layers
API Layer
- FastAPI Application (
main.py): Entry point for HTTP requests - API Routes (
endpoints/): RESTful endpoints organized by resource - Dependencies (
api/deps.py): Authentication and request validation
Service Layer
- Sync Service: Orchestrates data synchronization between sources and destinations
- DAG Service: Manages directed acyclic graphs for data transformations
- OAuth2 Service: Handles authentication for integrations
- Identity Provider (protocol): Abstracts user authentication, roles, and organization memberships (Auth0, Null, Fake adapters)
- Payment Gateway (protocol): Abstracts subscription management and billing operations (Stripe adapter)
- Resend Service: Manages transactional email delivery and templates
- PostHog Service: Manages product analytics and user event tracking
Data Access Layer
- CRUD Modules (
crud/): Database operations for each entity - Unit of Work: Transaction management with atomic operations
- Database Session: Async SQLAlchemy session management. This extra care must be applied with lazy objects and sessions.
Domain Layer
- Models (
models/): Database models (SQLAlchemy ORM) - Schemas (
schemas/): API data validation models (Pydantic)
Detail: short_name is a globally unique identifier used throughout the system, e.g. slack, outlook or hubspot_crm
Key Components
Platform Components
- Sources (
platform/sources/): Connectors to external data sources (APIs, DBs) - Destinations (
platform/destinations/): Vector database adapters - Embedding Models (
platform/embedding_models/): Text vectorization services - Transformers (
platform/transformers/): Data transformation processors - Entities (
platform/entities/): Core search objects that flow through the system
Sync Architecture
If necessary (like editing ), refer sync-architecture.mdc.
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.
- 4d ago First seen · 126 lines · 1,458 tokens per session scan A 26ca1ab70be8
backend-rules is a cursor rule published in the GitHub repository airweave-ai/airweave (6,565 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,458 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
development-phase
开发阶段：以新代码清晰合理为先，兼容仅在零代价时顺带.
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.