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-error-handling)<a href="https://agentmods.dev/rules/adobe/aem-desktop/security-global-error-handling"><img src="https://agentmods.dev/badge/rules/adobe/aem-desktop/security-global-error-handling/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-error-handling"><img src="https://agentmods.dev/badge/rules/adobe/aem-desktop/security-global-error-handling.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.00014 | $0.00252 |
| Opus 5.5 | $0.00006 | $0.00101 |
| Sonnet 5.5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
security-global-error-handling 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-error-handling — 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
Error Handling & Logging
Proper error handling and logging are critical for both security monitoring and preventing information leakage.
Secure Error Handling
- Implement centralized error handling
- Apply different handling for different environments
- Never expose stack traces or system details to users
- Provide user-friendly error messages
- Use appropriate HTTP status codes
Logging Best Practices
- Implement structured logging
- Log security-relevant events
- Include contextual information in logs
- Apply appropriate log levels
- Protect sensitive information in logs
Security Monitoring
- Implement centralized log collection
- Configure alerts for security events
- Establish baseline behavior patterns
- Implement automated log analysis
- Maintain audit trails for sensitive operations
Logging Security Events
- Authentication attempts (successful and failed)
- Authorization failures
- Input validation failures
- System configuration changes
- Data access and modification operations
Anti-Patterns to Avoid
- Exposing stack traces to end users
- Logging sensitive data (passwords, tokens, PII)
- Using inconsistent error handling approaches
- Neglecting to log security events
- Implementing custom logging solutions without security review
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 · 47 lines · 14 tokens per session scan A 41bff2ae7a4d
security-global-error-handling is a cursor rule published in the GitHub repository adobe/aem-desktop (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 252 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-error-handling, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.