An automated documentation workflow for Adobe Experience Manager (AEM), a system for building and managing website content. It configures a component, captures editor and website screenshots, and writes an authoring guide.

Use it to document completed AEM components with separate instructions for content editors and website visitors. It is invoked as part of specified AEM automation pipelines.

It removes the manual work of finding a documentation page, setting up the component, taking screenshots, and explaining how editors should use it.

aem-doc-gen — Skill for Claude Code by easingthemes

Install

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.

Clone the repo

git clone --depth 1 https://github.com/easingthemes/dx-aem-flow

agentmods

npx agentmods add skills/easingthemes/dx-aem-flow/aem-doc-gen

Made for: Claude Code.

Or install dx-aem, the plugin that ships this one along with the rest of its 12 skills, 6 agents, 1 hook, 2 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-doc-gen.svg)](https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-doc-gen)

Your own site

<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-doc-gen"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-doc-gen.svg" alt="Measured on agentmods" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,103 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00064	$0.03103
Opus 5	$0.00032	$0.01551
Sonnet 5	$0.00013	$0.00621
Haiku 4.5	$0.00006	$0.00310

Measured 8d ago against content hash 9b07943bb8e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

aem-doc-gen scanned grade A with 1 finding 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 8d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf -o /dev/null -w "%{http_code}" "$AUTHOR_URL/libs/granite/core/content/login.html" || echo "unreachable"

plugins/dx-aem/skills/aem-doc-gen/SKILL.md · 282 lines

How it starts

The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Platform note: This skill uses context: fork + agent: aem-editorial-guide-capture for isolated execution. If subagent dispatch is unavailable (e.g., VS Code Chat), you may run inline but AEM MCP tools (AEM/*, playwright/*) must be available. If they are not, inform the user: "AEM doc generation requires AEM and Playwright MCP servers. Please use Claude Code or Copilot CLI."

You generate AEM component demo documentation from completed spec files. You find or create a docs page, configure the component, capture dialog and website screenshots, and write an authoring guide with Authoring and Website sections.

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:

aem.author-url (defaults to http://localhost:4502)
aem.author-url-qa — QA author URL
aem.publish-url (defaults to http://localhost:4503)
aem.publish-url-qa — QA publisher URL
aem.resource-type-pattern — component resource type pattern
aem.demo-parent-path — parent path for all AI-created demo pages (e.g., /content/brand-a/ca/en/ca/en/demo)

2. Determine Environment

If PIPELINE_MODE=true (check via Bash: echo "$PIPELINE_MODE") or caller passes --qa: use aem.author-url-qa and aem.publish-url-qa
Otherwise: use aem.author-url and aem.publish-url
Fall back to local URLs if QA URLs are not configured

Set $AUTHOR_URL and $PUBLISH_URL for the rest of the flow.

3. Read Source Files

Read these files from $SPEC_DIR (all optional):

explain.md — what was implemented (to identify the component)
implement.md — plan steps (component names, file paths)
aem-after.md — post-deployment component state (dialog fields, properties, pages)
aem-before.md — pre-development baseline (fallback if aem-after.md missing)

4. Identify Component

Determine the target component name from spec files, in order of priority:

Read the full file on GitHub · 282 lines

Changes

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.

8d ago First seen · 282 lines · 64 tokens per session scan A 9b07943bb8e6

Subscribe to this mod's changes

aem-doc-gen is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 6d ago), licensed MIT. It adds 64 tokens to every session and 3,103 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens

aem-doc-gen