Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add easingthemes/dx-aem-flow/plugin install dx-coreWrote 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-axe)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-axe"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-axe.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.1 | $0.00048 | $0.02167 |
| Opus 5 | $0.00024 | $0.01084 |
| Sonnet 5 | $0.00010 | $0.00433 |
| Haiku 4.5 | $0.00005 | $0.00217 |
Grade A, and why
dx-axe 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 6d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You perform accessibility testing and remediation using the Deque axe MCP Server. You follow a strict analyze → remediate → fix → verify workflow.
1. Parse Arguments
Extract from $ARGUMENTS:
- URL (required) — the page URL to test
- --fix flag — if present, automatically apply remediation fixes to source code after analysis
- --standard — WCAG standard to test against (default:
wcag2aa)
If no URL is provided, ask the user for one.
2. Load axe MCP Tools
Use ToolSearch to discover the axe MCP Server tools:
ToolSearch query: "+axe analyze"
Look for tools matching axe_mcp_server__analyze and axe_mcp_server__remediate (or similar naming with axe prefix).
If not found, tell the user:
axe MCP Server not available. See setup guide:
docs/dx-axe.mdin the plugin repo. Quick checklist: Docker running?AXE_API_KEYexported? Image pulled (docker pull dequesystems/axe-mcp-server:latest)? Plugin reinstalled after setup?
Then STOP.
3. Resolve URL for axe
The axe MCP Server runs inside Docker. URLs must be reachable from the container.
Local AEM (localhost)
Replace localhost with host.docker.internal in the URL passed to axe — inside Docker, localhost is the container itself:
| User provides | Pass to axe |
|---|---|
http://localhost:4502/... |
http://host.docker.internal:4502/... |
http://admin:admin@localhost:4502/... |
http://admin:[email protected]:4502/... |
If the URL has no credentials and the host is localhost:4502, embed admin:admin (AEM default local credentials):
http://admin:[email protected]:4502/content/...?wcmmode=disabled
Remote AEM (QA / Stage)
Follow the qa-basic-auth rule. Resolve credentials in priority order:
- Env vars:
QA_BASIC_AUTH_USER/QA_BASIC_AUTH_PASS .ai/config.yamlkeysaem.qa-basic-auth.username/aem.qa-basic-auth.password
If credentials are found, embed them in the URL for the first navigation only — the session cookie persists for subsequent navigations:
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.
- 6d ago First seen · 233 lines · 48 tokens per session scan A 6a9ace0cf079
dx-axe is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 2,167 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…