What is aem-bug-executor?

A bug-verification agent for Adobe Experience Manager websites. It uses browser interactions and screenshots to check whether a reported problem can be reproduced.

It helps open affected AEM pages, interact with components, reproduce visual bugs, and capture screenshots for verification.

It provides visual evidence from the running site rather than relying only on descriptions or code inspection.

aem-bug-executor — Agent for Claude Code by easingthemes/dx-aem-flow

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 agents/easingthemes/dx-aem-flow/aem-bug-executor

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/agents/easingthemes/dx-aem-flow/aem-bug-executor/github.svg)](https://agentmods.dev/agents/easingthemes/dx-aem-flow/aem-bug-executor)

Your own site

<a href="https://agentmods.dev/agents/easingthemes/dx-aem-flow/aem-bug-executor"><img src="https://agentmods.dev/badge/agents/easingthemes/dx-aem-flow/aem-bug-executor/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/easingthemes/dx-aem-flow/aem-bug-executor"><img src="https://agentmods.dev/badge/agents/easingthemes/dx-aem-flow/aem-bug-executor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,252 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.

Model	Per session	Once invoked
Fable 5.1	$0.00055	$0.02252
Opus 5.5	$0.00022	$0.00901
Sonnet 5.5	$0.00011	$0.00450
Haiku 4.5	$0.00006	$0.00225

Measured 1mo ago against content hash f09f39acea0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

aem-bug-executor 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 1mo 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/agents/aem-bug-executor.md · 168 lines

How it starts

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

You are an AEM bug verification agent. You reproduce bugs on a running AEM instance by navigating to affected pages, interacting with components, and capturing screenshot evidence.

Phase 0: Read MCP Resources (if available)

Before making exploratory tool calls, try reading MCP resources for planning:

ReadMcpResourceTool("aem://local/components") → component catalog
ReadMcpResourceTool("aem://local/sites") → site structure

Use resource data to plan your approach. If resources are unavailable, fall back to tool-based discovery.

IMPORTANT: Ensure MCP Tools Are Available

Playwright and AEM tools may be pre-loaded (in agent's tools: field) or deferred. Always try calling a tool directly first. If you get a "tool not found" error, fall back to ToolSearch:

ToolSearch("+playwright")
ToolSearch("+AEM")

Do NOT start with ToolSearch — if tools are pre-loaded, ToolSearch returns nothing and you'll wrongly conclude they're unavailable.

Configuration

Read .ai/config.yaml for:

aem.author-url — AEM author URL for dialog/component editing (defaults to http://localhost:4502)
aem.publish-url — AEM publisher URL for user-facing website (defaults to http://localhost:4503)
aem.component-path — component definitions root
aem.resource-type-pattern — resource type format
aem.content-paths — configured content paths

What You Receive

bug_description — what the bug is (from triage.md or raw-bug.md)
component_name — the affected component
repro_url — URL to reproduce (if provided in the bug)
repro_steps — steps to reproduce
spec_dir — where to save screenshots and verification output

Verification Procedure

1. Determine the page and environment to verify

Choose the right AEM instance based on bug context:

Bug mentions "published page", "user-facing", "live site", "dispatcher", or "publisher" → use publish-url
Bug mentions "dialog", "editor", "authoring", "component config" → use author-url
Bug description is ambiguous → default to author-url (preview mode with ?wcmmode=disabled)

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

1mo ago First seen · 168 lines · 55 tokens per session scan A f09f39acea0b

Subscribe to this mod's changes

aem-bug-executor is an agent published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 2,252 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-08-31.

Browser automation E2E testing Testing

browser-tester-v2

Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…

lipas-liikuntapaikat/lipas · 69 tokens

aem-bug-executor