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/feature-flagsgit 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/feature-flags)<a href="https://agentmods.dev/rules/airweave-ai/airweave/feature-flags"><img src="https://agentmods.dev/badge/rules/airweave-ai/airweave/feature-flags.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.00723 |
| Opus 5 | $0.00000 | $0.00362 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
feature-flags 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Flags
Overview
Lightweight organization-level feature flags for gating features. Table name is feature_flag (org is implied).
Backend Usage
Enum (FeatureFlag)
from airweave.core.shared_models import FeatureFlag
# Check in endpoints via ApiContext
if not ctx.has_feature(FeatureFlag.S3_DESTINATION):
raise HTTPException(403, "Feature not available")
CRUD Operations
Integrated into crud.organization:
from airweave import crud
# Enable/disable flags
await crud.organization.enable_feature(db, org_id, FeatureFlag.S3_DESTINATION)
await crud.organization.disable_feature(db, org_id, FeatureFlag.WHITE_LABEL)
# Query flags
flags = await crud.organization.get_org_features(db, org_id)
# Bulk operations
await crud.organization.bulk_enable_features(db, org_id, [
FeatureFlag.S3_DESTINATION,
FeatureFlag.PRIORITY_SUPPORT
])
Schema Handling
Organization schemas automatically extract enabled_features from the feature_flags relationship using Pydantic validators (handles async context properly).
Frontend Usage
import { useOrganizationStore } from '@/lib/stores/organizations';
import { FeatureFlags } from '@/lib/constants/feature-flags';
const hasFeature = useOrganizationStore((state) => state.hasFeature);
{hasFeature(FeatureFlags.S3_DESTINATION) && <S3DestinationCard />}
Adding New Flags
- Add to
FeatureFlagenum inbackend/airweave/core/shared_models.py - Add to
FeatureFlagsconstants infrontend/src/lib/constants/feature-flags.ts - Enable for organizations via CRUD or admin panel
Feature Flags
Overview
Lightweight organization-level feature flags for gating features. Table name is feature_flag (org is implied).
Backend Usage
Enum (FeatureFlag)
from airweave.core.shared_models import FeatureFlag
# Check in endpoints via ApiContext
if not ctx.has_feature(FeatureFlag.S3_DESTINATION):
raise HTTPException(403, "Feature not available")
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 · 111 lines · 0 tokens per session scan A 7a722eaf7acc
feature-flags 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 723 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.