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/apisec-inc/apisec-skillsWrote 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/apisec-inc/apisec-skills/admin-rbac)<a href="https://agentmods.dev/rules/apisec-inc/apisec-skills/admin-rbac"><img src="https://agentmods.dev/badge/rules/apisec-inc/apisec-skills/admin-rbac/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/apisec-inc/apisec-skills/admin-rbac"><img src="https://agentmods.dev/badge/rules/apisec-inc/apisec-skills/admin-rbac.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.00196 | $0.00196 |
| Opus 5.5 | $0.00078 | $0.00078 |
| Sonnet 5.5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
admin-rbac 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 23d 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
Admin RBAC rule
Any endpoint or function that performs an admin-scoped operation, such as accessing all users, modifying system config, deleting records belonging to other users, or reading privileged data, must include an explicit role check before executing.
Authentication alone is not sufficient. Being logged in does not imply admin access.
Never generate admin operations that rely on implicit permission inheritance from authenticated state.
Required pattern: if (req.user.role !== 'admin') { return res.status(403).json({ error: 'Forbidden' }); }
This check must appear BEFORE any privileged operation. Generate it at the top of the handler, not nested inside logic.
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.
- 23d ago Changed · +2 tokens per session a73458942590
- 1mo ago First seen · 26 lines · 194 tokens per session scan A f26ceaf2c3db
admin-rbac is a cursor rule published in the GitHub repository apisec-inc/apisec-skills (21 stars, last pushed 23d ago), licensed MIT. It adds 196 tokens to every session, about $0.0008 per session on Opus 5.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
patchman
Patchman defensive security review defaults.
project-memory
This rule guides recording project events and decisions in projectmem.
mcpnuke-development
Core mcpnuke development standards and superpowers workflow integration.
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
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.