A read-only health check for Adobe Experience Manager project infrastructure, including components, OSGi settings, dispatcher rules, content structure, and Java code patterns.

Checking selected areas such as components, OSGi, dispatcher, content, code, or the whole AEM project and reporting warnings in a status table.

It helps identify configuration drift or infrastructure problems without changing, repairing, or deploying the project.

aem-doctor — Skill for Claude Code by easingthemes

Install

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.

Any agent

npx skills add easingthemes/dx-aem-flow --skill aem-doctor

Clone the repo

git clone --depth 1 https://github.com/easingthemes/dx-aem-flow

Made for: Claude Code.

Or install dx-aem, the plugin that ships this one along with the rest of its 12 skills, 6 agents, 1 hook, 2 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-doctor/github.svg)](https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-doctor)

Your own site

<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-doctor"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-doctor/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-doctor"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,570 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00043	$0.02570
Opus 5	$0.00022	$0.01285
Sonnet 5	$0.00009	$0.00514
Haiku 4.5	$0.00004	$0.00257

Measured 9d ago against content hash 7deb146814a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

aem-doctor 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 9d 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.

plugins/dx-aem/skills/aem-doctor/SKILL.md · 249 lines

How it starts

The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a diagnostic tool for AEM project infrastructure. You check local files, AEM instance state, and project conventions, then print a status table with warnings.

This skill is read-only. Never modify, fix, or deploy anything.

1. Read Configuration

Read .ai/config.yaml for:

aem.component-path — component definitions root (e.g., /apps/myproject/components/content/)
aem.resource-type-pattern — expected resource type format
aem.author-url — AEM instance URL (defaults to http://localhost:4502)
aem.frontend-dir — frontend source directory
aem.brands — configured brands (if multi-brand)
build.command — project build command

Also read the component index if it exists — check .ai/project/component-index.md first, fall back to .ai/component-index.md.

2. Determine Scope

Parse the argument:

components — check component definitions only
osgi — check OSGi configurations only
dispatcher — check dispatcher rules only
content — check AEM content structure only
code — check Java code for anti-patterns only
all or no argument — check everything

3. Run Checks

3a. Component Definition Integrity

For each component in the component path:

Verify structure:

# Find all component .content.xml files
find <component-path-in-repo> -name ".content.xml" -path "*components*"

Check each component has:

.content.xml with valid jcr:primaryType and componentGroup
_cq_dialog/.content.xml (dialog definition) — warn if missing
At least one .html (HTL template) — warn if missing
sling:resourceSuperType reference is valid (if set)

Cross-reference with component index: If the component index exists (.ai/project/component-index.md or .ai/component-index.md), verify:

All indexed components still exist on disk
No new (unindexed) components have been added
Resource types match between index and .content.xml

3b. OSGi Configuration Integrity

Search for OSGi config directories:

find . -path "*/osgiconfig/*" -name "*.cfg.json" -o -name "*.config" | head -30

Read the full file on GitHub · 249 lines

Changes

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.

9d ago First seen · 249 lines · 43 tokens per session scan A 7deb146814a7

Subscribe to this mod's changes

aem-doctor is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 8d ago), licensed MIT. It adds 43 tokens to every session and 2,570 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Debugging

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens