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/apisec-inc/apisec-skills/auth-requiredgit 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/auth-required)<a href="https://agentmods.dev/rules/apisec-inc/apisec-skills/auth-required"><img src="https://agentmods.dev/badge/rules/apisec-inc/apisec-skills/auth-required.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 | $0.00251 | $0.00251 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
auth-required 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 3d 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
API authentication rule
Every route handler that reads, modifies, or deletes data MUST include authentication middleware or a decorator before the handler executes.
Never generate a data-touching endpoint without auth. If auth middleware is not yet defined in the codebase, note that it needs to be added and generate a placeholder that fails safely (401) until implemented.
Patterns that indicate missing auth — flag these:
- Express route with no middleware before the handler function
- FastAPI endpoint with no Depends(get_current_user) or equivalent
- Django view with no @login_required or IsAuthenticated permission class
- Spring endpoint with no @PreAuthorize or SecurityConfig coverage
- Go handler registered without auth middleware in the route group
When you detect missing auth, do not silently generate the insecure code. Output: ⚠️ Auth missing — add authentication before generating this endpoint. Suggested fix: [framework-appropriate auth middleware pattern]
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.
- 3d ago First seen · 28 lines · 251 tokens per session scan A 99787a93a795
auth-required is a cursor rule published in the GitHub repository apisec-inc/apisec-skills (18 stars, last pushed 5mo ago), licensed MIT. It adds 251 tokens to every session, about $0.0013 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.