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/integrations-yamlgit 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/integrations-yaml)<a href="https://agentmods.dev/rules/airweave-ai/airweave/integrations-yaml"><img src="https://agentmods.dev/badge/rules/airweave-ai/airweave/integrations-yaml.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.01903 |
| Opus 5 | $0.00000 | $0.00951 |
| Sonnet 5 | $0.00000 | $0.00381 |
| Haiku 4.5 | $0.00000 | $0.00190 |
Grade A, and why
integrations-yaml 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 6d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airweave Integrations Configuration Structure
YAML Configuration Structure
The <env>.integrations.yaml files define authentication configurations for various third-party service integrations. The structure follows this pattern:
integrations:
service_name:
auth_type: "oauth2_with_refresh" # or other auth types
url: "https://service.com/oauth/authorize"
backend_url: "https://service.com/oauth/token"
grant_type: "authorization_code"
client_id: "client_id_here"
client_secret: "client_secret_here"
content_type: "application/x-www-form-urlencoded"
client_credential_location: "body" # or "header"
scope: "scope1 scope2 scope3" # service-specific bot/app permissions
user_scope: "user_scope1 user_scope2" # optional, user-specific permissions (Slack, etc.)
requires_pkce: false # optional, default false. Set true for PKCE-required providers (e.g., Airtable)
additional_frontend_params: # optional service-specific parameters
param1: "value1"
param2: "value2"
Example Integrations
Standard OAuth (Gmail):
gmail:
auth_type: "oauth2_with_refresh"
url: "https://accounts.google.com/o/oauth2/auth"
backend_url: "https://oauth2.googleapis.com/token"
grant_type: "authorization_code"
client_id: "502433363466-d8ruvkdb3nkafulj63tnenn8iud31sks.apps.googleusercontent.com"
client_secret: "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"
content_type: "application/x-www-form-urlencoded"
client_credential_location: "body"
scope: "https://www.googleapis.com/auth/gmail.readonly"
additional_frontend_params:
access_type: "offline"
prompt: "consent"
OAuth with PKCE (Airtable):
airtable:
oauth_type: "with_refresh"
url: "https://airtable.com/oauth2/v1/authorize"
backend_url: "https://airtable.com/oauth2/v1/token"
grant_type: "authorization_code"
client_id: "your-client-id"
client_secret: "your-client-secret"
content_type: "application/x-www-form-urlencoded"
client_credential_location: "header"
scope: "schema.bases:read data.records:read"
requires_pkce: true # PKCE (Proof Key for Code Exchange) prevents authorization code interception
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.
- 6d ago First seen · 198 lines · 1,903 tokens per session scan A 98179f08a3c8
integrations-yaml 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 1,903 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
开发阶段：以新代码清晰合理为先，兼容仅在零代价时顺带.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.