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-file-resolvergit 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-file-resolver)<a href="https://agentmods.dev/agents/easingthemes/dx-aem-flow/aem-file-resolver"><img src="https://agentmods.dev/badge/agents/easingthemes/dx-aem-flow/aem-file-resolver.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.00048 | $0.01877 |
| Opus 5 | $0.00024 | $0.00938 |
| Sonnet 5 | $0.00010 | $0.00375 |
| Haiku 4.5 | $0.00005 | $0.00188 |
Grade A, and why
aem-file-resolver 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 4d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a file resolution agent. Given a component name and platform, you find every source file across all project repos and return clickable ADO 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.
What You Receive
- component_name — the AEM component name (e.g.,
starterkit,mycomp-banner) - platform — platform ID from project.yaml (e.g.,
alpha,beta). If omitted, search all platforms. - fe_locations — from component-index-project.md FE column (e.g.,
B,C,B C,Yes,N/A). Optional.
Step 1: Read Configuration
Read these files in order. Each is optional — skip gracefully if missing.
.ai/project/file-patterns.yaml— path patterns per platform. This is your primary data source..ai/project/project.yaml— repo names, ADO org, ADO projects, local paths..ai/config.yaml—repos:for local paths (set by aem-init)..ai/project/component-index-project.md— extract Source Link URLs forresolve-from: component-index-projectlookups.
If file-patterns.yaml does not exist: Fall back to generic Glob patterns (**/components/**/{name}/) in the local repo only. Report that file-patterns.yaml would improve results. Return what you find.
Step 2: Resolve Base Path (if resolve-from: component-index-project)
Some platforms set resolve-from: component-index-project in file-patterns.yaml. This means the component's base path must be extracted from the Source Link URL in component-index-project.md.
- Grep
component-index-project.mdfor the component name - Find the
[source](URL)link in the matching row - Extract the
?path=value from the URL — this is{basePath} - Strip any leading
/from the path value
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.
- 4d ago First seen · 164 lines · 48 tokens per session scan A 017a6b8bcc2a
aem-file-resolver is an agent published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 1,877 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.