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.
git 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/auth-providers)<a href="https://agentmods.dev/rules/airweave-ai/airweave/auth-providers"><img src="https://agentmods.dev/badge/rules/airweave-ai/airweave/auth-providers/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/airweave-ai/airweave/auth-providers"><img src="https://agentmods.dev/badge/rules/airweave-ai/airweave/auth-providers.svg" alt="Reviewed on agentmods" width="80" 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.01110 |
| Opus 5.5 | $0.00000 | $0.00444 |
| Sonnet 5.5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
auth-providers 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 1mo 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airweave Auth Providers
Overview
Auth providers enable third-party services (Pipedream, Composio) to supply credentials for source connections, eliminating manual credential management and enabling OAuth at scale for agent developers who are already using these connector providers.
Architecture
Core Components
domains/auth_provider/
├── _base.py # BaseAuthProvider abstract class
├── auth_result.py # AuthResult dataclass
├── exceptions.py # Typed exception hierarchy
├── protocols.py # Domain protocols
├── registry.py # Provider discovery/registration
├── service.py # AuthProviderService
├── types.py # Shared type aliases
├── providers/
│ ├── composio.py # API key provider
│ ├── klavis.py # Future provider
│ └── pipedream.py # OAuth2 provider (tokens expire in 3600s)
└── tests/
Provider Registration
@auth_provider(
name="Pipedream",
short_name="pipedream",
auth_config_class=PipedreamAuthConfig,
config_class=PipedreamConfig,
)
class PipedreamAuthProvider(BaseAuthProvider):
async def create(credentials, config): ...
async def get_creds_for_source(source_short_name, fields): ...
Provider Configuration
Providers have several configuration mechanisms:
Field Mappings
Map between Airweave and external service naming:
# Map Airweave field names to provider field names
FIELD_NAME_MAPPING = {"api_key": "generic_api_key", "personal_access_token": "access_token"}
# Map Airweave source names to provider source names (only needed when names differ)
SLUG_NAME_MAPPING = {
"google_drive": "googledrive",
"google_slides": "googleslides",
"outlook_mail": "outlook"
}
Integration with TokenProviderProtocol
Auth providers integrate via AuthProviderTokenProvider, one of three TokenProviderProtocol implementations:
Protocol hierarchy
SourceAuthProvider (Protocol) — base: provider_kind + supports_refresh
├── TokenProviderProtocol (Protocol) — get_token() + force_refresh()
│ ├── OAuthTokenProvider — expiry-aware refresh, DB-backed
│ ├── StaticTokenProvider — raw string / API key (no refresh)
│ └── AuthProviderTokenProvider — delegates to Pipedream / Composio
└── DirectCredentialProvider[T] — structured creds (NTLM, client_credentials)
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.
- 1mo ago First seen · 125 lines · 1,110 tokens per session scan A 768703f79b28
auth-providers is a cursor rule published in the GitHub repository airweave-ai/airweave (6,552 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,110 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
vibes-plug-devops
Vibes-Plug Cloud & DevOps Platform Engineering — Docker BuildKit, distroless runtimes, Kubernetes GitOps, and GitHub Actions OIDC.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.