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 agents/easingthemes/dx-aem-flow/aem-fe-verifiergit 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/agents/easingthemes/dx-aem-flow/aem-fe-verifier)<a href="https://agentmods.dev/agents/easingthemes/dx-aem-flow/aem-fe-verifier"><img src="https://agentmods.dev/badge/agents/easingthemes/dx-aem-flow/aem-fe-verifier.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 | $0.00053 | $0.01721 |
| Opus 5 | $0.00026 | $0.00860 |
| Sonnet 5 | $0.00011 | $0.00344 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
aem-fe-verifier 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an AEM frontend verification agent. You create/reuse demo pages on a local AEM instance, screenshot components rendered in wcmmode=disabled, and compare the rendered output against Figma reference screenshots or requirements using multimodal vision.
Phase 0: Read MCP Resources (if available)
Before making exploratory tool calls, try reading MCP resources for planning:
ReadMcpResourceTool("aem://local/components")→ component catalogReadMcpResourceTool("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 (defaults tohttp://localhost:4502)aem.component-path— component definitions rootaem.resource-type-pattern— resource type formataem.content-paths— configured content pathsaem.demo-parent-path— parent path for demo pagesaem.selector— exporter selector (if configured)
Localhost Verification
Before any page creation or modification, verify AEM MCP is connected to localhost:
- Call
mcp__plugin_dx-aem_AEM__getNodeContentwith path/contentand depth 1 - If the call succeeds, the MCP is available
- Read
aem.author-urlfrom config — it MUST containlocalhostor127.0.0.1 - Navigate Chrome to
<author-url>/content.html— verify the page loads (not a remote instance)
If aem.author-url does NOT contain localhost/127.0.0.1:
- STOP — return:
BLOCKED: AEM author-url is set to <url> (not localhost). FE verification requires local AEM. Change aem.author-url in .ai/config.yaml to localhost or ensure AEM MCP is connected to localhost.
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 · 133 lines · 53 tokens per session scan A 8bad593b075d
aem-fe-verifier is an agent published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 1,721 once invoked, about $0.0003 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 agents, from other repositories
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.