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 skills add easingthemes/dx-aem-flow --skill dx-doctorgit clone --depth 1 https://github.com/easingthemes/dx-aem-flowWrote 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/skills/easingthemes/dx-aem-flow/dx-doctor)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-doctor"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-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.
<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-doctor"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 87 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 279 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00040 | $0.06350 |
| Opus 5.5 | $0.00016 | $0.02540 |
| Sonnet 5.5 | $0.00008 | $0.01270 |
| Haiku 4.5 | $0.00004 | $0.00635 |
Grade A, and why
dx-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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 557 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a diagnostic tool for the dx workflow setup in a consumer project. You check all init-generated files across all installed plugins, then print a status report with actionable remediation.
This skill is read-only. Never modify, fix, or create anything.
Tool Usage Rules
- File existence: Use
Globwith exact path patterns — never[ -f ],test -f, orlsin Bash - File content: Use
Readto read files — nevercat,head, ordiffin Bash - Content comparison: Read both files with
Read, compare in-context — never shelldiff - Bash is ONLY for:
git branch -a(step 6a) — nothing else in this skill needs Bash - Parallel checks: Call multiple
Glob/Readtools in a single response for efficiency — do not serialize into one Bash command with&&/||
0. Read Configuration & Detect Plugins
Read .ai/config.yaml. If it does not exist:
✗ FATAL: .ai/config.yaml not found. Run /dx-init first.
STOP.
Detect which plugins are configured:
- dx — always (config.yaml exists)
- aem —
aem:section present in config.yaml - seed-data —
.ai/project/directory exists with seed data files - auto —
.ai/automation/infra.jsonexists
Parse the argument:
dx— check dx core onlyaem— check AEM plugin onlyseed-dataordata— check seed data onlyauto— check automation plugin onlyallor no argument — check everything
If the user requests a specific plugin that is not configured, report: ⚠ <plugin> plugin not configured. Skipping.
1. dx Core Files
Check existence and validity of every file dx-init generates.
1a. Config Structure
Read .ai/config.yaml and verify these required keys exist and are non-empty:
project.nameproject.prefixscm.providerscm.orgscm.base-branchbuild.command
Report each: ✓ present or ✗ MISSING.
1a-ii. Config Version
Read dx.version from .ai/config.yaml:
- Missing →
⚠ dx.version not set — run /dx-upgrade to add version tracking - Older than current plugin version →
⚠ Config version <version> behind plugin <plugin-version> — run /dx-upgrade - Current →
✓ dx.version: <version>
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.
- yesterday Changed cc73aac8f2ed
- 2d ago Changed · +5 lines · -3 tokens per session fb427b0fa01f
- 1mo ago Changed · +2 lines ca215307de6a
- 1mo ago First seen · 550 lines · 43 tokens per session scan A 583907269f27
dx-doctor is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 6,350 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
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…
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.
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…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.