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/token-provider-exceptionsgit 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/token-provider-exceptions)<a href="https://agentmods.dev/rules/airweave-ai/airweave/token-provider-exceptions"><img src="https://agentmods.dev/badge/rules/airweave-ai/airweave/token-provider-exceptions.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.01070 |
| Opus 5 | $0.00000 | $0.00535 |
| Sonnet 5 | $0.00000 | $0.00214 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
token-provider-exceptions 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Token Provider Exceptions → Source Connection Actionability
Three exception layers
OAuth2 token endpoint / Auth provider API
↓ raises typed domain exceptions
OAuthRefreshServerError, OAuthRefreshTokenRevokedError, ... (domains/oauth/exceptions.py)
AuthProviderAccountNotFoundError, AuthProviderAuthError, ... (platform/auth_providers/exceptions.py)
↓ token providers catch + translate
TokenCredentialsInvalidError, TokenProviderAccountGoneError, ... (domains/sources/token_providers/exceptions.py)
↓ each carries:
.provider_kind ("oauth" | "auth_provider" | "static")
.source_short_name
.__cause__ (original exception)
Token provider exception hierarchy
TokenProviderError (SourceError)
├── TokenExpiredError — token is known-dead, cannot be refreshed (fast abort)
├── TokenCredentialsInvalidError — token/refresh_token expired or revoked
├── TokenProviderAccountGoneError — external record deleted (Composio/Pipedream)
│ .account_id
├── TokenProviderConfigError — fundamental misconfiguration
├── TokenProviderMissingCredsError — response missing required fields
│ .missing_fields
├── TokenProviderRateLimitError — upstream rate-limiting
│ .retry_after
├── TokenProviderServerError — 5xx / timeout / connection error from credential source
│ .status_code
└── TokenRefreshNotSupportedError — static token / no refresh_token
TokenExpiredError is raised by get_token() when the provider knows the token is dead and refresh is impossible (e.g. the refresh_token itself is revoked). Callers should treat it as a permanent failure and surface NEEDS_REAUTH immediately without retrying.
How the SC domain makes this actionable
Connection status expansion
class SourceConnectionStatus(str, Enum):
ACTIVE = "active"
PENDING_AUTH = "pending_auth"
SYNCING = "syncing"
PENDING_SYNC = "pending_sync"
NEEDS_REAUTH = "needs_reauth" # ← credentials expired/revoked, user must re-authenticate
ERROR = "error" # ← config/permanent errors
INACTIVE = "inactive"
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 · 96 lines · 0 tokens per session scan A 278278d2c6a8
token-provider-exceptions 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,070 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-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.