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 skills/easingthemes/dx-aem-flow/aem-initnpx skills add easingthemes/dx-aem-flow --skill aem-initgit 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/aem-init)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-init"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-init.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.07591 |
| Opus 5 | $0.00022 | $0.03795 |
| Sonnet 5 | $0.00009 | $0.01518 |
| Haiku 4.5 | $0.00004 | $0.00759 |
Grade A, and why
aem-init 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 629 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You configure AEM-specific settings by detecting the project structure and appending an aem: section to .ai/config.yaml.
Re-run Validation Protocol
CRITICAL: When aem-init is re-run, EVERY step MUST execute. NEVER stop early. If the user chooses "Keep as-is" for config, skip to step 6 and continue through ALL remaining steps (6→7→8→9). Each step validates:
| File Category | Re-run Behavior |
|---|---|
| Config (aem: section in config.yaml) | Ask: keep / modify / regenerate |
| Component index (.ai/project/component-index.md) | Offer to re-scan if stale |
| Component discovery (.ai/project/component-discovery.md) | Offer to re-scan if stale (AEM dialog changes on QA) |
| Shared rule extensions (pr-review.md, pr-answer.md AEM sections) | Validate sections exist, re-append if missing |
| Rule templates (.claude/rules/be-.md, fe-.md) | Compare against plugin template → if template changed and user hasn't customized: update. If user customized: show diff, ask |
| Copilot instructions | Read from .claude/rules/ via COPILOT_CUSTOM_INSTRUCTIONS_DIRS — no copies needed |
| Copilot agents (.github/agents/AEM*.md) | Compare against plugin template → update silently if changed |
Inline execution from dx-init: When this skill is run inline from
/dx-initstep 7 (AEM auto-chain), skip Copilot-related steps: 8a (Copilot question), 8e (AEM Copilot agent templates), and 8f (copilot-instructions.md update). Also skip step 9 (Confirm). These are handled by dx-init steps 9 and 10 instead. SetCOPILOT_ENABLED=falseas default — dx-init handles Copilot output separately.
1. Check Prerequisites
Check if .ai/config.yaml exists. If not: "Run /dx-init first to set up the base project config."
Check if .ai/config.yaml already has an aem: section:
- If it exists: Display current AEM config and ask: "AEM config already exists. (A) Keep as-is, (B) Modify, or (C) Regenerate?"
- If A: Say "Config kept. Validating all AEM files..." — then CONTINUE to step 6 to validate component index, rules, and templates. DO NOT stop or exit.
- If B/C: Continue to step 2
- If it doesn't exist: Continue to step 2.
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.
- 4d ago First seen · 629 lines · 44 tokens per session scan A ad19bd952375
aem-init is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 7,591 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…