Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/easingthemes/dx-aem-flownpx agentmods add skills/easingthemes/dx-aem-flow/dx-doc-retroWrote 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/dx-doc-retro)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-doc-retro"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-doc-retro/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-doc-retro"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-doc-retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.03603 |
| Opus 5.5 | $0.00024 | $0.01441 |
| Sonnet 5.5 | $0.00012 | $0.00721 |
| Haiku 4.5 | $0.00006 | $0.00360 |
Grade A, and why
dx-doc-retro 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 2d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You generate technical documentation for stories that are already implemented. Unlike /dx-doc-gen (which reads spec files produced during development), this skill discovers everything from the ADO work item and linked PRs. Posts to ADO Wiki or Confluence depending on tracker.provider.
1. Parse Input
Extract the numeric work item ID from the argument. Accept:
- Numeric ID:
2357516 - Full URL:
https://dev.azure.com/{org}/{project}/_workitems/edit/2357516 - Short URL:
https://<org>.visualstudio.com/.../_workitems/edit/2357516
If no argument, ask the user for it.
Read .ai/config.yaml for:
tracker.provider—ado(default) orjirascm.org,scm.project,scm.repo-idscm.wiki-id,scm.wiki-project,scm.wiki-doc-rootconfluence.space-key,confluence.doc-root(if provider = jira)
2. Fetch Work Item
mcp__ado__wit_work_item
action: "get"
project: <scm.project>
id: <work item ID>
expand: "Relations"
Extract:
- Title, ID, State, Type
- Iteration Path → sprint name (last segment, normalize
Sprint41→Sprint 41) - Description → markdown
- Acceptance Criteria → markdown
- Relations → find PR links (artifact links with
vstfs:///Git/PullRequestId/URLs)
Save sprint to memory for step 6.
If the work item is not found or is not a User Story/Bug, print the error and STOP.
3. Find Linked PRs
From the relations, extract Pull Request artifact links. The URL format is:
vstfs:///Git/PullRequestId/{projectId}%2F{repoId}%2F{pullRequestId}
For each PR link, extract the pullRequestId and fetch:
mcp__ado__repo_pull_request
action: "get"
repositoryId: <scm.repo-id>
pullRequestId: <extracted PR ID>
Filter: Only keep PRs whose status is completed (discard abandoned, active, and all other non-completed statuses) and whose repository matches scm.repo-id (or any repo in repos: config). Discard PRs to unrelated repos.
For each relevant PR, collect:
- PR title, ID, source branch, target branch
- PR description (often contains implementation notes)
- Merge commit or last merge source commit
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.
- 2d ago Changed · +1 lines a35b9be30ea2
- 19d ago Changed · +2 lines 55f4f27d76dc
- 1mo ago First seen · 300 lines · 61 tokens per session scan A 940006591b41
dx-doc-retro is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 3,603 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…