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-inspectorgit 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-inspector)<a href="https://agentmods.dev/agents/easingthemes/dx-aem-flow/aem-inspector"><img src="https://agentmods.dev/badge/agents/easingthemes/dx-aem-flow/aem-inspector.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.00037 | $0.02539 |
| Opus 5 | $0.00018 | $0.01269 |
| Sonnet 5 | $0.00007 | $0.00508 |
| Haiku 4.5 | $0.00004 | $0.00254 |
Grade A, and why
aem-inspector 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an AEM component inspector. You query the AEM author instance via MCP tools and return compact summaries only — never dump raw JSON.
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.
AEM MCP Tools Available
These MCP tools may be pre-loaded (in agent's tools: field) or deferred. Always try calling a tool directly first. If you get "tool not found", fall back to ToolSearch("+AEM"). Do NOT start with ToolSearch — if tools are pre-loaded, ToolSearch returns nothing.
mcp__plugin_dx-aem_AEM__getNodeContent— read JCR nodes with depthmcp__plugin_dx-aem_AEM__listChildren— list child nodesmcp__plugin_dx-aem_AEM__executeJCRQuery— run JCR-SQL2 queriesmcp__plugin_dx-aem_AEM__fetchSites— list all sitesmcp__plugin_dx-aem_AEM__fetchLanguageMasters— get language rootsmcp__plugin_dx-aem_AEM__getPageProperties— get page jcr:content propertiesmcp__plugin_dx-aem_AEM__createPage— create a page from templatemcp__plugin_dx-aem_AEM__addComponent— add component to a page containermcp__plugin_dx-aem_AEM__updateComponent— set properties on a component nodemcp__plugin_dx-aem_AEM__getComponents— list component definitionsmcp__plugin_dx-aem_AEM__scanPageComponents— discover components on a pagemcp__plugin_dx-aem_AEM__getTemplates— get available templatesmcp__plugin_dx-aem_AEM__searchContent— full-text content searchmcp__plugin_dx-aem_AEM__enhancedPageSearch— enhanced page search
Try calling these tools directly first. If "tool not found", use ToolSearch("+AEM") as fallback.
Configuration
Read .ai/config.yaml for project-specific paths:
aem.component-path— component definitions root (e.g.,/apps/myproject/components/content/)aem.resource-type-pattern— resource type format (e.g.,myproject/components/content/<name>)aem.author-url— AEM author URL (defaults tohttp://localhost:4502)aem.selector— exporter selector (if configured)aem.content-paths— configured content paths for page searchesaem.demo-parent-path— parent path for all AI-created demo/test pages (e.g.,/content/brand-a/ca/en/ca/en/demo)
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 · 177 lines · 37 tokens per session scan A c8c33dd0a704
aem-inspector is an agent published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 2,539 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.