AEM Desktop is an Electron desktop application for Adobe Experience Manager Edge Delivery Services, with development infrastructure for hot reload, updates, testing, and macOS release builds. It is used by developers building and releasing the desktop client, including signed and notarized macOS packages. Its catalogue entries provide coding-agent rules and instructions for working in this repository.
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/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-data-protection)<a href="https://agentmods.dev/rules/adobe/aem-desktop/security-global-data-protection"><img src="https://agentmods.dev/badge/rules/adobe/aem-desktop/security-global-data-protection/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/adobe/aem-desktop/security-global-data-protection"><img src="https://agentmods.dev/badge/rules/adobe/aem-desktop/security-global-data-protection.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.00020 | $0.00308 |
| Opus 5.5 | $0.00008 | $0.00123 |
| Sonnet 5.5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
security-global-data-protection 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.
This is a copy
100% identical to security-global-data-protection — 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
Data Protection & Privacy
These rules apply throughout the application and aimed at maintaining data security and privacy throughout the application.
Data Classification
- Classify data based on sensitivity
- Apply appropriate controls based on classification
- Document data flows and storage locations
- Implement data minimization principles
Encryption
Data in Transit
- Use TLS 1.2+ for all connections
- Configure secure TLS settings
- Enforce HTTPS through HSTS
- Apply proper certificate management
- Validate certificates
Data at Rest
- Encrypt sensitive data before storage
- Use strong encryption algorithms (AES-256, ChaCha20)
- Implement proper key management
- Consider using envelope encryption
- Rotate encryption keys periodically
Key Management
- Securely store encryption keys
- Separate keys from encrypted data
- Implement key rotation procedures
- Use a key management service when possible
- Apply the principle of least privilege to key access
Data Minimization & Privacy
- Collect only necessary data
- Implement data retention policies
- Provide mechanisms for data export and deletion
- Implement consent management
- Apply privacy by design principles
Anti-Patterns to Avoid
- Storing sensitive data in plaintext
- Hardcoding encryption keys or secrets
- Implementing custom encryption algorithms
- Failing to validate certificates
- Storing sensitive data in logs or error messages
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 · 57 lines · 20 tokens per session scan A cd996de2e9bd
security-global-data-protection is a cursor rule published in the GitHub repository adobe/aem-desktop (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 308 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to security-global-data-protection, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.
hatch3r-data-classification
Data classification standards covering PII handling, encryption, retention policies, and regulatory compliance.
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.