agentmods.dev

aem-editorial-guide

aem-editorial-guide is a skill for Claude Code from easingthemes/dx-aem-flow. It costs 46 tokens per session (2,195 once invoked), scanned A, original, MIT.

A documentation workflow for an Adobe Experience Manager (AEM) component's editing dialog. It opens the component in the AEM editor, captures a screenshot, and writes instructions for content editors.

In plain words
What is it for?
Use it after verifying or deploying an AEM component to document its editable fields and how authors should use it. It can infer the component and page from recent specification files.
Why use it?
It removes the manual work of demonstrating dialog fields and turning them into an editor-friendly guide after a component change.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter; mentions subagents; mentions Claude Code.

Part of the dx-aem plugin — 12 skills, 6 agents, 1 hook, 2 MCP servers shipped together

not rated 6repo 6d ago A scan 46 tokens original MIT

Good fit Use it after verifying or deploying an AEM component to document its editable fields and how authors should use it. It can infer the component and page from recent specification files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/easingthemes/dx-aem-flow/aem-editorial-guide
View source ↗ easingthemes/dx-aem-flow
Install

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.

Any agent
npx skills add easingthemes/dx-aem-flow --skill aem-editorial-guide
Clone the repo
git clone --depth 1 https://github.com/easingthemes/dx-aem-flow

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.

agentmods badge for aem-editorial-guide

README.md
[![agentmods](https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-editorial-guide.svg)](https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-editorial-guide)
Your own site
<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-editorial-guide"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-editorial-guide.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,195 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.02195
Opus 5 $0.00023 $0.01097
Sonnet 5 $0.00009 $0.00439
Haiku 4.5 $0.00005 $0.00219

Measured 7d ago against content hash 6f0d96cf9c7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

aem-editorial-guide 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 7d 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.

plugins/dx-aem/skills/aem-editorial-guide/SKILL.md · 202 lines

How it starts

The opening of the file, as written. The whole thing — 202 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 demo capture requires AEM and Playwright MCP servers. Please use Claude Code or Copilot CLI."

Task

Capture a demo of the AEM component $ARGUMENTS — open its dialog in the AEM editor, take a screenshot, and write an editor-friendly authoring guide.

If no component name was provided, check .ai/specs/*-*/aem-after.md or .ai/specs/*-*/aem-before.md to infer it. If unclear, state what you need and stop.

Steps

1. Find the page and spec directory

Read .ai/config.yaml for aem.author-url (defaults to http://localhost:4502) and aem.resource-type-pattern.

Read the most recent .ai/specs/*-*/aem-after.md (or aem-before.md) to find:

  • A page path where the component is authored
  • The component name and new/changed fields

If no aem-after.md exists, use AEM MCP tools:

  • mcp__plugin_dx-aem_AEM__searchContent with fulltext $ARGUMENTS under /content, limit 5
  • Pick the most recently modified page

Also identify the spec directory path for saving output.

2. Ensure demo folder exists

Create <spec-dir>/demo/ if it doesn't exist.

3. Open the page in AEM editor

Navigate Chrome to <author-url>/editor.html<page-path>.html.

Authenticate the author (preferred — no password in context): bash .ai/lib/aem-playwright-auth.sh author <local|qa> → browser_set_storage_state with .ai/playwright/aem-author-state.json → navigate (already logged in).

Fallback — login redirect: if a navigation still lands on /libs/granite/core/content/login.html, log in:

  1. Use browser_evaluate to fill #username and #password with AEM credentials resolved from AEM_INSTANCES (bash .ai/lib/dx-common.sh aem-instance <local|qa>; falls back to admin/admin for localhost only)
  2. Dispatch input events after setting values so Coral UI registers them
  3. Use browser_evaluate to click #submit-button
  4. Wait for the editor page to load (use browser_wait_for with the page title or "Edit", timeout 15 seconds)

Read the full file on GitHub · 202 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.

  1. 7d ago First seen · 202 lines · 46 tokens per session scan A 6f0d96cf9c7f

Subscribe to this mod's changes

aem-editorial-guide is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 2,195 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.

Writing and docs
Related

Other skills, from other repositories

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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens