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/AlphaBitCore/nexus-gatewayWrote 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/alphabitcore/nexus-gateway/iam-impact-review)<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/iam-impact-review"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/iam-impact-review.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.00536 |
| Opus 5 | $0.00000 | $0.00268 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
iam-impact-review 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.
What it actually says
IAM impact review (binding)
You are editing an area where adding / moving / renaming an admin API endpoint, sidebar nav, or route path can produce silent 403s. The UI / backend / seed must stay in lockstep.
Read docs/developers/architecture/services/control-plane/iam-identity-architecture.md BEFORE editing.
The 5-step audit (all 5, every change)
- UI
allowedActionsand backendiamMW(...)reference the same action. Drift = silent 403 (user sees menu item, click yields 403). - Decide resource carve-out. Should the surface have its own resource type in
packages/shared/identity/iam/catalog_data.go, or can it reusesettings/observability/ etc.? Carve out when granting it shouldn't imply granting unrelated settings. - New resource → update both fixtures + seed.
packages/control-plane/internal/identity/iam/managed.go(NexusViewertest fixture).tools/db-migrate/seed/seed.tscanonical policy block.- Missing either makes non-super-admin users lose visibility silently.
- Path rename / move → sweep Sidebar + breadcrumbs.
packages/control-plane-ui/src/components/ui/Sidebar/Sidebar.tsxicon mapping. Deadcasearms accumulate otherwise. - Record IAM decisions in the plan / commit message. "Kept on
admin:settings.read" / "Carved out asprompt-cache" — so reviewers can trace policy intent without reading the diff backwards.
NRN builder is canonical
Always use iam.BuildRequestNRNForAction(action, c) to derive resourceType. Never hardcode the resource-type string in iamMW(...) — hardcoded resource types drift from the IAM catalog and produce silent 403s. Memory anchor: [[project_iam_resource_nrn_bug]].
Verification
Run positive test (super-admin reaches the route) AND negative test (a role without the action gets 403). Don't ship without both.
Skipping this rule requires explicit user approval in chat.
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 · 38 lines · 0 tokens per session scan A 1eb69d549027
iam-impact-review is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (23 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 536 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
skill-mcp-server
Padrões DARE para servidores MCP (Model Context Protocol da Anthropic) em TypeScript ou Python. Tools, resources, prompts; transports stdio/SSE/HTTP; validação Zod/Pydantic; autorização por tool; observabilidade; testes; publicação.
skill-laravel-api
Padrões Globais para Projetos Laravel API (Context Engineering).
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.