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-secure-configuration)<a href="https://agentmods.dev/rules/adobe/aem-desktop/security-global-secure-configuration"><img src="https://agentmods.dev/badge/rules/adobe/aem-desktop/security-global-secure-configuration/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-secure-configuration"><img src="https://agentmods.dev/badge/rules/adobe/aem-desktop/security-global-secure-configuration.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.00015 | $0.00266 |
| Opus 5.5 | $0.00006 | $0.00106 |
| Sonnet 5.5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
security-global-secure-configuration 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-secure-configuration — 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
Configuration & Infrastructure
Secure configuration is foundational to application security, influencing how systems are deployed and maintained.
Environment Configuration
- Use environment-specific configuration files
- Implement secure defaults for all environments
- Minimize configuration differences between environments
- Document all configuration options
- Apply infrastructure as code principles
Secrets Management
- Never hardcode secrets in source code
- Use dedicated secrets management tools
- Implement secure secret rotation
- Apply principle of least privilege for secrets access
- Audit secret access and usage
Containerization Security
- Use minimal base images
- Run containers as non-root users
- Implement container security scanning
- Apply resource restrictions
- Keep container images updated
Security Headers & Settings
- Implement secure HTTP headers (X-Content-Type-Options, X-Frame-Options)
- Configure Content Security Policy
- Apply cookie security attributes
- Configure CORS policies appropriately
- Disable directory listings
Anti-Patterns to Avoid
- Using default passwords or credentials
- Exposing unnecessary services or ports
- Enabling unnecessary features or modules
- Using insecure defaults
- Failing to harden infrastructure components
- Neglecting consistent configuration across environments
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 · 48 lines · 15 tokens per session scan A 1b6078fada5d
security-global-secure-configuration is a cursor rule published in the GitHub repository adobe/aem-desktop (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 266 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-secure-configuration, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
hack
Hack is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
container-rightsizer
Rightsizes container CPU and memory requests and limits using real usage data. Reduces requested resources without hitting OOMKills or CPU throttling.