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-secure-configurationgit clone --depth 1 https://github.com/adobe/aem-desktopWhat 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.00266 |
| Opus 5 | $0.00008 | $0.00133 |
| Sonnet 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 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.
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.
- 2d 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 7d ago), licensed Apache-2.0. It adds 15 tokens to every session and 266 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-secure-configuration, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
backend
Backend development rules for TT Studio - AI model management backend.
devops-infrastructure
DevOps and infrastructure: Docker, Kubernetes, Terraform, CI/CD. Load when editing Dockerfiles, compose, k8s manifests, Terraform, or workflow YAML — not for application code.
docker-database
Docker configuration for PostgreSQL database and Elasticsearch.
hack
Hack v3 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.
colima-docker-runtime
This workspace uses Colima for Docker; use compose-backed tests when Colima is running.