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/eliornl/rolemule/auth-patternsgit clone --depth 1 https://github.com/eliornl/rolemuleWhat 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.00000 | $0.03431 |
| Opus 5 | $0.00000 | $0.01716 |
| Sonnet 5 | $0.00000 | $0.00686 |
| Haiku 4.5 | $0.00000 | $0.00343 |
Grade A, and why
auth-patterns 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 2d 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authentication Patterns
JWT Token Structure
Every issued token always includes jti (unique ID for revocation), iat (issued-at), nbf (not-before), type, and exp:
{
"sub": user_id,
"email": user_email,
"type": "access", # always present — prevents password-reset tokens being used as session tokens
"exp": expiration_datetime,
"iat": issued_at_datetime,
"nbf": issued_at_datetime, # reject tokens used before they were issued
"jti": "uuid4-string" # required for revocation
}
_validate_jwt_token() in utils/auth.py rejects any token whose type is present but is not "access". This prevents one-time tokens (password-reset, email-verify) from being replayed as session credentials.
Creating Tokens — Use _make_jwt in api/auth.py
Never call jwt.encode directly inside api/auth.py. Use the central helper:
access_token = _make_jwt(
{"sub": str(user.id), "email": user.email},
expire_hours=security_settings.jwt_config["expire_hours"],
)
_make_jwt automatically adds jti, iat, and exp.
For utility code outside api/auth.py, use create_access_token from utils/auth.py:
from utils.auth import create_access_token
token = create_access_token({"sub": user_id, "email": email})
All Auth Endpoints
| Endpoint | Method | Description |
|---|---|---|
/api/v1/auth/register |
POST | Create account → sends verification + welcome email |
/api/v1/auth/login |
POST | Login with account lockout protection |
/api/v1/auth/refresh |
POST | Refresh JWT |
/api/v1/auth/verify |
GET | Verify current token |
/api/v1/auth/logout |
POST | Logout — revokes the JWT via Redis blocklist |
/api/v1/auth/forgot-password |
POST | Request password reset email |
/api/v1/auth/reset-password |
POST | Reset password with token |
/api/v1/auth/change-password |
PUT | Change password (authenticated) |
/api/v1/auth/email-status |
GET | Check if SMTP is configured |
/api/v1/auth/verify-email |
GET | Verify email with token |
/api/v1/auth/verify-code |
POST | Verify email with 6-digit code |
/api/v1/auth/resend-verification |
POST | Resend verification email |
/api/v1/auth/verification-status |
GET | Check verification status |
/api/v1/auth/google |
GET | Initiate Google OAuth |
/api/v1/auth/google/callback |
GET | OAuth callback — redirects with ?code= |
/api/v1/auth/oauth/exchange-code |
POST | Exchange one-time OAuth code for JWT |
/api/v1/auth/extension-status |
GET | Auth status for Chrome extension |
/api/v1/auth/tokens |
POST | Create personal access token (rm_pat_…) — plaintext shown once |
/api/v1/auth/tokens |
GET | List PATs (metadata only; no plaintext) |
/api/v1/auth/tokens/{id} |
DELETE | Revoke one PAT |
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.
- 2d ago First seen · 333 lines · 0 tokens per session scan A 4171a2ce1fd5
auth-patterns is a cursor rule published in the GitHub repository eliornl/rolemule (37 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,431 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
cursorrules
Agent2 is a framework for building production AI agents with typed HTTP APIs. PydanticAI handles the agent loop. Agent2 handles everything else: API, auth, pause/resume, approvals, provider routing, knowledge search.
product-manager
Holistic product leader who owns the full product lifecycle — from discovery and strategy through roadmap, stakeholder alignment, go-to-market, and outcome measurement. Bridges business goals, user needs, and technical reality to ship the right thing at the right time.
api-tester
Expert API testing specialist focused on comprehensive API validation, performance testing, and quality assurance across all systems and third-party integrations.
developer-advocate
Expert developer advocate specializing in building developer communities, creating compelling technical content, optimizing developer experience (DX), and driving platform adoption through authentic engineering engagement. Bridges product and engineering teams with external developers.
architectural-and-structural-rules
The project follows a layered architecture with clear separation of concerns.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.