Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/easingthemes/dx-aem-flownpx agentmods add skills/easingthemes/dx-aem-flow/dx-doc-genWrote 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-doc-gen)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-doc-gen"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-doc-gen/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-doc-gen"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-doc-gen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.04400 |
| Opus 5.5 | $0.00027 | $0.01760 |
| Sonnet 5.5 | $0.00014 | $0.00880 |
| Haiku 4.5 | $0.00007 | $0.00440 |
Grade A, and why
dx-doc-gen 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You generate wiki-style documentation from completed spec files. The output captures what was built, why, and how to use it. In pipeline/wiki mode, it posts to the correct sprint subfolder in the ADO wiki or Confluence (depending on tracker.provider).
1. Locate the Spec Directory
SPEC_DIR=$(bash .ai/lib/dx-common.sh find-spec-dir <work-item-id-if-provided>)
If the script exits with error, ask the user for the work item ID.
Read .ai/config.yaml for:
tracker.provider—ado(default) orjirascm.org— ADO org URLscm.project— ADO project namescm.wiki-id— ADO wiki identifier (if configured)scm.wiki-project— project that owns the wiki (may differ fromscm.project)scm.wiki-doc-root— root wiki path for technical documentationconfluence.space-key— Confluence space key (if provider = jira)confluence.doc-root— parent page title for generated docs (if provider = jira)
2. Read Source Files
Read these files from $SPEC_DIR (all optional — generate from what's available):
raw-story.md— original story for title, ID, acceptance criteria, iteration pathexplain.md— distilled developer requirementsshare-plan.md— non-technical summaryimplement.md— step-by-step plan with statusresearch.md— codebase context and patterns found.sprint— sprint name (e.g.,Sprint 41) saved by/dx-req(Phase 1).branch— feature branch name.pr— PR number and URL (if PR was created)demo/authoring-guide.md— AEM authoring guide with screenshots (produced by/aem-doc-gen)figma-extract.md— Figma design data (produced by/dx-figma-extract)aem-fe-verify.md— FE verification verdict (produced by/aem-fe-verify)aem-after.md— post-deployment component state (produced by/aem-verify)qa-handoff.md— QA testing steps with page URLs (produced by/aem-qa-handoff)
If none exist (excluding authoring-guide.md), print "No spec files found — nothing to generate from. For a story finished without dx spec files, run /dx-doc-retro <id>." and STOP.
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 · +17 tokens per session 3221bd7d597a
- 2d ago Changed · -1 lines · -12 tokens per session 2c9ad84b930f
- 19d ago Changed · +2 lines 2743047c3b09
- 1mo ago First seen · 310 lines · 63 tokens per session scan A a5ed0772c2ba
dx-doc-gen is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 4,400 once invoked, about $0.0003 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…