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 skills add easingthemes/dx-aem-flow --skill dx-pr-review-reportgit 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/dx-pr-review-report)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-pr-review-report"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-pr-review-report/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-pr-review-report"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-pr-review-report.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.00060 | $0.03688 |
| Opus 5.5 | $0.00024 | $0.01475 |
| Sonnet 5.5 | $0.00012 | $0.00738 |
| Haiku 4.5 | $0.00006 | $0.00369 |
Grade A, and why
dx-pr-review-report 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You generate a structured report from an existing PR review. The report groups review comments by category, summarizes patch outcomes, and optionally posts to the ADO wiki.
Defaults
Read shared/ado-config.md and shared/provider-config.md for how to look up project config from .ai/config.yaml.
- Provider: read from
.ai/config.yamltracker.provider—ado(default) orjira - Organization: read from
.ai/config.yamlscm.org— NEVER hardcode - Project: read from
.ai/config.yamlscm.project - Wiki parent page (ADO): read from
.ai/config.yamlscm.wiki-pr-review-root— parent wiki page for PR review reports - Confluence space (Jira): read from
.ai/config.yamlconfluence.space-key - Confluence PR review root (Jira): read from
.ai/config.yamlconfluence.pr-review-root— parent page title for PR review reports
1. Parse Input
The argument is either:
- Full URL:
https://{org}.visualstudio.com/{project}/_git/{repo}/pullrequest/{id}orhttps://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{id}— extractproject,repo, andpullRequestId. URL-decode the project. The URL-extracted project takes precedence over the config default. - PR ID only (number): Detect repo from
git remote get-url origin, read.ai/config.yamlfor repo → ADO project mapping
Load MCP tools before any ADO calls:
ToolSearch("+ado repo")
ToolSearch("+ado pull request thread")
ToolSearch("+ado wiki")
ToolSearch("+ado work item")
2. Fetch PR Details
Resolve the repo ID first:
mcp__ado__repo_repository
action: "get"
project: "<project from URL if provided, otherwise from config>"
repositoryNameOrId: "<repo name>"
Then fetch the PR:
mcp__ado__repo_pull_request
action: "get"
repositoryId: "<repo ID>"
pullRequestId: <PR ID>
Extract:
- Title, PR ID, Author (displayName)
- Source branch, Target branch
- Status (active, completed, abandoned)
- Created date, Closed date (if completed)
- Reviewers and their votes
- Description — for understanding the PR intent
- Work item links — from
resourceRefrelations (artifact links withvstfs:///Git/PullRequestId/)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +2 tokens per session b9fa1a08a84a
- 19d ago Changed · +10 lines 0a87390ac05c
- 1mo ago Changed 3b143a0b283e
- 1mo ago First seen · 368 lines · 58 tokens per session scan A 8d9f965947f8
dx-pr-review-report is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 3,688 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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…