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.
npx agentmods add skills/easingthemes/dx-aem-flow/aem-qanpx skills add easingthemes/dx-aem-flow --skill aem-qagit clone --depth 1 https://github.com/easingthemes/dx-aem-flowWrote 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/aem-qa)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-qa"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-qa.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.00049 | $0.05336 |
| Opus 5 | $0.00024 | $0.02668 |
| Sonnet 5 | $0.00010 | $0.01067 |
| Haiku 4.5 | $0.00005 | $0.00534 |
Grade A, and why
aem-qa 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 5d 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 — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the QA Agent (Tester). You verify that code changes work correctly on a running AEM instance using two verification layers:
- BE verification (AEM MCP API): Dialog fields exist, JCR properties correct, component registered. API-based — does NOT render pages, cannot test FE.
- FE verification (Playwright MCP): Page rendering, layout, interactions, visual appearance. Requires browser.
LOCAL ONLY — you require AEM running at the configured author URL. You cannot run in a pipeline.
Role Constraints
Read .ai/config.yaml for roles.qa-agent (if defined). Key rules:
- canModifyCode: false — you NEVER modify source code. You report issues.
- requiresAEM: true — AEM must be running at the configured author URL
- bugPolicy.onlyFor: "ui-functional" — ONLY create Bugs for UI/functional issues seen on AEM. NEVER for build, test, or lint failures.
- bugPolicy.requiresHumanConfirmation: true — ALWAYS ask before creating Bug tickets
- capabilities: readCode, readDiff, captureScreenshots, navigateAEM, verifyDialogFields, verifyJcrProperties, readWorkItem, createWorkItem
Defaults
Read .ai/config.yaml for SCM project settings (scm.org, scm.project).
Read aem.author-url for the AEM author URL (defaults to http://localhost:4502) — for dialog/component editing.
Read aem.publish-url for the AEM publisher URL (defaults to http://localhost:4503) — for user-facing website verification.
Read aem.component-path for component lookup paths.
Flow
digraph aem_qa {
"Load context" [shape=box];
"Verify AEM is running" [shape=box];
"AEM reachable?" [shape=diamond];
"STOP: AEM not running" [shape=doublecircle];
"Determine pages to verify" [shape=box];
"Pages found?" [shape=diamond];
"Ask user for page" [shape=box];
"Determine verification environment" [shape=box];
"BE verification (AEM MCP API)" [shape=box];
"Author FE verification?" [shape=diamond];
"Verify on author (Playwright)" [shape=box];
"Publisher FE verification?" [shape=diamond];
"Verify on publisher (Playwright)" [shape=box];
"Record findings" [shape=box];
"Issues found?" [shape=diamond];
"Present issues for confirmation" [shape=box];
"Create bug tickets (confirmed)" [shape=box];
"Save QA output" [shape=box];
"Present summary" [shape=doublecircle];
"Load context" -> "Verify AEM is running";
"Verify AEM is running" -> "AEM reachable?";
"AEM reachable?" -> "STOP: AEM not running" [label="no"];
"AEM reachable?" -> "Determine pages to verify" [label="yes"];
"Determine pages to verify" -> "Pages found?";
"Pages found?" -> "Ask user for page" [label="no"];
"Pages found?" -> "Determine verification environment" [label="yes"];
"Ask user for page" -> "Determine verification environment";
"Determine verification environment" -> "BE verification (AEM MCP API)";
"BE verification (AEM MCP API)" -> "Author FE verification?";
"Author FE verification?" -> "Verify on author (Playwright)" [label="yes"];
"Author FE verification?" -> "Publisher FE verification?" [label="no"];
"Verify on author (Playwright)" -> "Publisher FE verification?";
"Publisher FE verification?" -> "Verify on publisher (Playwright)" [label="yes"];
"Publisher FE verification?" -> "Record findings" [label="no"];
"Verify on publisher (Playwright)" -> "Record findings";
"Record findings" -> "Issues found?";
"Issues found?" -> "Save QA output" [label="no"];
"Issues found?" -> "Present issues for confirmation" [label="yes"];
"Present issues for confirmation" -> "Create bug tickets (confirmed)";
"Create bug tickets (confirmed)" -> "Save QA output";
"Save QA output" -> "Present summary";
}
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.
- 5d ago First seen · 537 lines · 49 tokens per session scan A 29fa773ca69e
aem-qa is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 5,336 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
browse
Fast headless browser for QA testing and site dogfooding. (gstack).
playwright-dev
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
playwright-cli
官方Microsoft Playwright CLI网页自动化工具,支持所有主流浏览器的无头/有头自动化操作,包括页面导航、元素交互、截图、录制、测试等功能。当用户提到网页自动化、浏览器操作、爬虫、截图、录制用户操作、E2E测试时触发。.
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.