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-ejectgit 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-eject)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-eject"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-eject/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-eject"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-eject.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.00056 | $0.03445 |
| Opus 5.5 | $0.00022 | $0.01378 |
| Sonnet 5.5 | $0.00011 | $0.00689 |
| Haiku 4.5 | $0.00006 | $0.00345 |
Grade A, and why
dx-eject 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You eject (copy) all plugin assets into the consumer project so it can operate independently without any dx plugins installed. This is a one-way, irreversible operation — after ejecting, the project owns all files and plugin updates no longer propagate automatically.
Tool Usage Rules
- File existence: Use
Glob— never[ -f ],test -f, or Bash test commands - File content reads: Use
Read— nevercatorheadin Bash - File writes: Use
WriteorEdit— neverecho >in Bash - Bash is ONLY for: running
eject.sh,chmod +x,gitcommands, and install scripts - Parallel operations: Call multiple
Read/Write/Globtools in parallel when independent
0. Pre-flight Checks
0a. Verify dx is initialized
Check that .ai/config.yaml exists (use Glob). If not:
✗ FATAL: .ai/config.yaml not found. Run /dx-init first before ejecting.
STOP.
0b. Resolve Plugin Directories
Find each installed plugin root:
- dx plugin: Glob for
**/skills/dx-doctor/SKILL.md, navigate up 3 levels - aem plugin: Glob for
**/skills/aem-init/SKILL.md, navigate up 3 levels - auto plugin: Glob for
**/skills/auto-init/SKILL.md, navigate up 3 levels
Parse the argument to determine scope:
dx— eject dx-core onlyaem— eject dx-aem onlyauto— eject dx-automation onlyallor no argument — eject all detected plugins
If a requested plugin is not found, report: ⚠ <plugin> plugin not detected. Skipping.
0c. Warn the User
Present this warning and wait for explicit confirmation:
## ⚠ Eject Warning
This will copy ALL assets from the following plugins into your repo:
- dx-core (49 skills, 7 agents, 5 rules, shared files, data, templates)
- dx-hub (5 skills, data, templates)
- dx-aem (12 skills, 6 agents, shared files, templates)
- dx-automation (10 skills, 1 rule, data files, templates)
### What happens:
1. **Claude Code skills** → `.claude/skills/` (shadows plugin skills — Claude Code loads local over plugin)
2. **Claude Code agents** → `.claude/agents/` (local agent definitions)
3. **Copilot agents** → `.github/agents/`
4. **Plugin originals** → `.ai/ejected/` (rules, shared, data, templates, hooks, manifests)
6. **Hooks config** → merged into `.claude/hooks.json`
### After ejecting:
- You can uninstall the plugins (`/plugin uninstall dx-core`, etc.)
- All skills and agents work from local files
- You are responsible for maintaining and updating these files
- `/dx-upgrade` and `/dx-doctor` will no longer work (they depend on plugin directories)
- To get plugin updates, you must manually diff and merge
**This cannot be undone. Proceed?** (yes/no)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +1 lines 85a690192f57
- 2d ago Changed · +1 lines ca2ac5e943b3
- 1mo ago First seen · 297 lines · 56 tokens per session scan A 3cefa18614eb
dx-eject is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 3,445 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…