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-api)<a href="https://agentmods.dev/rules/adobe/aem-desktop/security-global-api"><img src="https://agentmods.dev/badge/rules/adobe/aem-desktop/security-global-api/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-api"><img src="https://agentmods.dev/badge/rules/adobe/aem-desktop/security-global-api.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.00021 | $0.00456 |
| Opus 5.5 | $0.00008 | $0.00182 |
| Sonnet 5.5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
security-global-api 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-api — 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
API Security
These rules apply to Secure API design and implementation and it is critical for protecting data and services.
Secure API design
- Version endpoints using semantic versioning (
/v1/,/v2/,/v3/,/v4/) - Grant only the minimum permissions needed for each endpoint
- Document required authentication method and specific permission scopes in OpenAPI/Swagger
- Re-use security patterns across endpoints for consistency
- Return consistent HTTP status codes and error messages following RFC 7807
Auth & access
- Require OAuth 2.0 / JWT for user authentication
- Validate tokens on every request with proper signature verification
- Enforce Role-Based Access Control (RBAC) or Attribute-Based Access Control (ABAC)
- Issue API keys with specific scopes for service-to-service calls
- Implement token refresh with secure rotation
Request protection
- Apply rate‑limit & throttle
- Validate request schema using JSON Schema or similar validation
- Configure CORS to allow only specific origins, methods, and headers
- Check content-type headers and validate request structure
- Block parameter pollution attacks by validating parameter names
Security Headers
- Set
X-Content-Type-Options: nosniff - Set
X-Frame-Options: DENYorX-Frame-Options: SAMEORIGIN - Set
X-XSS-Protection: 1; mode=block - Implement Content Security Policy (CSP) headers
- Use
Strict-Transport-Securityfor HTTPS enforcement
Test & monitor
- Run API‑focused security tests
- Log security findings and fix critical issues
- Track & fix findings
Anti-Patterns to Avoid
- Leaking sensitive data in API responses (PII, tokens, internal errors)
- Allowing insecure direct object references without access checks
- Serving APIs over HTTP (always use HTTPS)
- Skipping input validation on any endpoint
- Revealing stack traces or internal system details in error responses
- Using weak authentication methods (Basic Auth, API keys without scopes)
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 · 51 lines · 21 tokens per session scan A bc5510baa27b
security-global-api is a cursor rule published in the GitHub repository adobe/aem-desktop (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 456 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-api, differing in 0 lines, and is treated as a copy.
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).