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-refreshnpx skills add easingthemes/dx-aem-flow --skill aem-refreshgit 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-refresh)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/aem-refresh"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/aem-refresh.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.00031 | $0.01347 |
| Opus 5 | $0.00015 | $0.00674 |
| Sonnet 5 | $0.00006 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
aem-refresh 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You refresh .ai/project/ data files from an external source. This updates the project knowledge that agents use for component lookups, file resolution, and market-scoped searches.
Source Resolution (three-source fallback)
1. User-provided local path (argument)
If the user passes a local path as argument:
- Verify the path exists
- Look for known file structure (see file table below)
- Copy files to
.ai/project/
2. Remote ADO docs repo
If no argument provided:
- Read
.ai/config.yaml→aem.docs-repofor the ADO repo URL - If set, use
mcp__ado__search_codeor ADO MCP file content tools to fetch each file by path - Default source paths in the docs repo (configurable via
aem.docs-repo-pathsin config.yaml):
| Source Path (in docs repo) | Destination | Mandatory |
|---|---|---|
docs/components/component-index.md |
.ai/project/component-index-project.md |
yes |
docs/project.yaml |
.ai/project/project.yaml |
yes |
docs/file-patterns.yaml |
.ai/project/file-patterns.yaml |
yes |
docs/content-paths.yaml |
.ai/project/content-paths.yaml |
no |
docs/architecture.md |
.ai/project/architecture.md |
yes |
docs/features.md |
.ai/project/features.md |
yes |
If aem.docs-repo-paths is set in config.yaml, use those paths instead.
3. No source available
If neither a local path nor aem.docs-repo is configured:
- Report error: "No seed data source available. Pass a local path as argument, or set
aem.docs-repoin.ai/config.yamlvia/aem-init." - Do NOT fall back to bundled data — there is no bundled seed data.
Copy Procedure
For each file in the table:
- Check if source file exists at the expected path
- If exists: copy to
.ai/project/destination - If not exists and mandatory: report warning
- If not exists and optional: skip silently
Create .ai/project/ directory if it doesn't exist.
Never overwrite component-index.md (the aem-init auto-generated local index). Only write to component-index-project.md (the enriched cross-repo index).
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 · 108 lines · 31 tokens per session scan A bab23a2a2a73
aem-refresh is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 1,347 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…