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/adobe/aem-desktop/security-global-injection-preventiongit clone --depth 1 https://github.com/adobe/aem-desktopWrote 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/adobe/aem-desktop/security-global-injection-prevention)<a href="https://agentmods.dev/rules/adobe/aem-desktop/security-global-injection-prevention"><img src="https://agentmods.dev/badge/rules/adobe/aem-desktop/security-global-injection-prevention.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.00015 | $0.00293 |
| Opus 5 | $0.00008 | $0.00147 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
security-global-injection-prevention 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.
This is a copy
100% identical to security-global-injection-prevention — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Injection Prevention
Injection vulnerabilities are among the most common and dangerous security issues in web applications.
Types of Injection Attacks
SQL Injection
- Use parameterized queries or prepared statements
- Apply ORM frameworks with proper escaping
- Implement input validation and sanitization
- Avoid dynamic SQL construction
Command Injection
- Avoid passing user input to system commands
- Use safer alternatives to shell execution
- Validate and sanitize all command parameters
- Apply allowlists for permitted commands
Cross-Site Scripting (XSS)
- Apply context-specific output encoding
- Implement Content Security Policy (CSP)
- Use modern frameworks with built-in XSS protection
- Sanitize HTML content
XML/XPATH Injection
- Use safe XML parsers
- Disable external entity processing
- Validate and sanitize XML input
- Apply parameterized XPATH queries
Framework-Specific Protections
- Use template engines that auto-escape content
- Apply framework-specific security features
- Keep frameworks and libraries updated
- Follow security best practices for your stack
Anti-Patterns to Avoid
- Using
eval()or similar functions - Constructing dynamic queries with string concatenation
- Directly using user input in commands
- Trusting client-side sanitization only
- Bypassing built-in security features
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 · 53 lines · 15 tokens per session scan A f375934ea992
security-global-injection-prevention is a cursor rule published in the GitHub repository adobe/aem-desktop (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 15 tokens to every session and 293 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to security-global-injection-prevention, differing in 0 lines, and is treated as a copy.
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.