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/netlify/context-and-toolsWrote 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/netlify/context-and-tools/netlify-identity-authorization-and-sessions)<a href="https://agentmods.dev/rules/netlify/context-and-tools/netlify-identity-authorization-and-sessions"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-identity-authorization-and-sessions.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.00019 | $0.00733 |
| Opus 5 | $0.00010 | $0.00367 |
| Sonnet 5 | $0.00004 | $0.00147 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
netlify-identity-authorization-and-sessions 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 8d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Netlify Identity — authorization and session gotchas
Where role-based access actually gets enforced, and why a role change doesn't take effect immediately.
Admin operations run only in the Functions runtime
Identity's admin API — creating users, updating a user's roles or metadata, deleting users (the admin.* operations) — requires a privileged admin token that is available only in the Netlify Functions runtime. It is not exposed to browser code and is not available in Edge Functions. Do all role assignment and user administration from inside a modern v2 Function (or an Identity event function), never from the client and never from an edge function. A "promote this user to admin" button in the UI must call a Function endpoint that performs the change server-side — it cannot call the admin API directly from the browser.
You don't configure or read the admin token yourself — the Netlify Functions runtime provides it automatically to admin.* calls made inside a Function, so there is no env var to set and no Netlify.env.get(...) to call for it. Run the admin.* operations server-side in a Function; never hardcode an admin token, ship one in the client bundle, or expose the admin operations to the browser. Exposing an admin capability client-side would let any visitor grant themselves the admin role.
Redirect gating only covers CDN document requests
conditions = { Role = [...] } redirects are enforced by the CDN only when it serves a document (navigation) request — a fresh HTTP request for the path. They are a coarse page-level perimeter, not real authorization:
- SPA client-side navigation bypasses them. When a client-side router (React, Vue, SvelteKit, etc.) navigates to
/adminin the browser, no new document request reaches the CDN, so the redirect rule never runs and the route renders regardless of the user's role. - Anything in the client bundle is downloadable by anyone. Role-gated content compiled into the JavaScript bundle ships to every visitor who can load the page; hiding a component behind a client-side role check does not protect the data inside it.
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.
- 8d ago First seen · 29 lines · 19 tokens per session scan A 2726edb13375
netlify-identity-authorization-and-sessions is a cursor rule published in the GitHub repository netlify/context-and-tools (36 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 733 once invoked, about $0.0001 per session on Opus 5. 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
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.