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/adobedocs/ff-services-docs/security-global-authgit clone --depth 1 https://github.com/AdobeDocs/ff-services-docsWhat 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.00015 | $0.00480 |
| Opus 5 | $0.00008 | $0.00240 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
security-global-auth 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- security-global-auth — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authentication & Authorization
Secure authentication and authorization are essential for protecting user data and system resources.
Authentication Best Practices
Password Management
- Implement strong password requirements (minimum 12 characters, must include uppercase, lowercase, numbers, and special characters)
- Store passwords using strong, slow hashing algorithms (bcrypt with 12+ rounds, Argon2)
- Never store plaintext passwords in any form
- Implement account lockout after 5 failed attempts with 30-minute lockout period
Multi-Factor Authentication
- Implement MFA for all user accounts, especially admin users and users with financial access
- Support multiple second-factor options (TOTP, SMS, email, hardware tokens)
- Apply MFA to critical operations (password resets, financial transactions, admin actions, data exports)
- Verify MFA on the server side, never trust client-side validation
Session Management
- Generate strong, random session identifiers (32+ characters using cryptographically secure random)
- Implement secure cookie attributes (Secure, HttpOnly, SameSite=Strict)
- Apply appropriate session timeouts (15 minutes for sensitive operations, 2 hours for regular sessions)
- Invalidate sessions on logout and password change
- Regenerate session IDs after authentication
- Implement mechanisms to revoke sessions remotely
Authorization Best Practices
Access Control Models
- Implement Role-Based Access Control (RBAC) with resource-level permissions (read, write, delete)
- Apply the principle of least privilege for all users
- Use attribute-based access control for fine-grained permissions
- Centralize authorization logic in dedicated services
Implementation Patterns
- Verify authorization on every request, including API calls
- Implement authorization checks at multiple layers (frontend UI, API middleware, database row-level security)
- Apply consistent authorization across all interfaces (API, UI, CLI)
- Never rely on client-side authorization alone
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 · 58 lines · 15 tokens per session scan A 46d4e0b6a5c0
security-global-auth is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 480 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-31.
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.