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/AdobeDocs/ff-services-docsWrote 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/adobedocs/ff-services-docs/security-global-base)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/security-global-base"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/security-global-base/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/adobedocs/ff-services-docs/security-global-base"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/security-global-base.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.00638 | $0.00638 |
| Opus 5.5 | $0.00255 | $0.00255 |
| Sonnet 5.5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
security-global-base 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 1mo 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-base — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
These rules define essential practices for writing and generating secure code.
They apply universally — to manual development, automated tooling, and AI-generated code.
Our codebase follows a security‑first mindset: security is built in from day one.
All violations must include a clear explanation of which rule was triggered and why, to help developers understand and fix the issue effectively.
Core Security Principles
1. Defense in Depth
- Implement multiple layers of security controls
- Apply security at every level (UI, API, database, infrastructure)
- Never rely on a single security measure
2. Principle of Least Privilege
- Grant minimal access required for functionality
- Use role-based access control (RBAC)
- Limit permissions to the smallest scope necessary
3. Fail Securely
- Default to secure state when errors occur
- Implement graceful degradation
- Never expose sensitive information in error messages
4. Secure by Default
- Ship secure configurations without extra setup
- Enable security features automatically
- Require explicit opt-out for insecure options
5. Keep It Simple
- Reduce complexity to minimize attack surface
- Avoid over-engineering security solutions
- Use proven, well-tested security patterns
Critical Security Rules
1. Do Not Use Raw User Input in Sensitive Operations
- Rule: Untrusted input must never be used directly in file access, command execution, database queries, or similar sensitive operations.
2. Do Not Expose Secrets in Public Code
- Rule: Secrets such as API keys, credentials, private keys, or tokens must not appear in frontend code, public repositories, or client-distributed files.
3. Enforce Secure Communication Protocols
- Rule: Only secure protocols (e.g., HTTPS, TLS) must be used for all external communications.
4. Avoid Executing Dynamic Code
- Rule: Dynamically constructed code or expressions must not be executed at runtime.
5. Validate All External Input
- Rule: Inputs from users, external APIs, or third-party systems must be validated before use.
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.
- 1mo ago First seen · 77 lines · 638 tokens per session scan A caa12169275a
security-global-base is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 638 tokens to every session, about $0.0026 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-31.
Other cursor rules, from other repositories
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).