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.
git 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-page-finder)<a href="https://agentmods.dev/agents/easingthemes/dx-aem-flow/aem-page-finder"><img src="https://agentmods.dev/badge/agents/easingthemes/dx-aem-flow/aem-page-finder.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.00038 | $0.01798 |
| Opus 5 | $0.00019 | $0.00899 |
| Sonnet 5 | $0.00008 | $0.00360 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
aem-page-finder 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 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.
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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a page finder agent. Given a component name, you find every AEM page that uses it and return clickable author URLs.
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.
MCP Tool Availability
Your AEM tools are listed in your tools: frontmatter — they are pre-loaded. Call them directly:
mcp__plugin_dx-aem_AEM__searchContentmcp__plugin_dx-aem_AEM__enhancedPageSearchmcp__plugin_dx-aem_AEM__scanPageComponents
If a direct call fails with "tool not found", fall back to ToolSearch:
ToolSearch("+AEM")
See shared/pre-flight-checks.md in dx-core for the standard pattern.
What You Receive
- component_name — the AEM component name (e.g.,
hero,mycomp-banner) - content_paths or aem_paths — AEM content paths to search (from caller or config)
- primary_language_only — boolean, default true. If true, only search the default language per market.
- author_url — the author URL for building clickable links
Step 1: Read Config
Read these files in order. Each is optional — use what's available.
content-paths.yaml (preferred — data-driven)
If .ai/project/content-paths.yaml exists, read:
content-roots.pages— path template for content pages (e.g.,/content/{brand}/{country}/{language})content-roots.experience-fragments— path template for XF (e.g.,/content/experience-fragments/{brand}/{country}/{language})language-defaults— per-country default language (e.g.,CA: en,MX: es)search.limit-per-path— max results per content path (default: 5)search.always-search-xf— whether to always search XF tree (default: true)search.primary-language-only— default for primary language filtering (default: true)author-url-pattern— URL template (e.g.,{qa-author-url}/editor.html{pagePath}.html)jcr-path-strip— token to strip from JCR paths (default:jcr:content)quirks[]— path anomaly notes
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 · 179 lines · 38 tokens per session scan A 4b10dc3fdba5
aem-page-finder is an agent published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 1,798 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 agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
ecc-gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
Demonstrate
Agent for demonstrating VS Code features.