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-allgit 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-all)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-pr-review-all"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-pr-review-all/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-all"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-pr-review-all.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00032 | $0.05957 |
| Opus 5.5 | $0.00013 | $0.02383 |
| Sonnet 5.5 | $0.00006 | $0.01191 |
| Haiku 4.5 | $0.00003 | $0.00596 |
Grade C, and why
dx-pr-review-all scanned grade C with 1 finding 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 19d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/dx-review-<repo> How it starts
The opening of the file, as written. The whole thing — 614 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You list active Azure DevOps pull requests, present them for selection, then review each one using /dx-pr-review — which supports posting comments, proposing fix patches, and following up on author responses.
Flow
digraph pr_reviews {
"Parse input" [shape=box];
"Input type?" [shape=diamond];
"Delegate to dx-pr-review" [shape=doublecircle];
"Load MCP tools + resolve repo" [shape=box];
"List active PRs" [shape=box];
"PRs found?" [shape=diamond];
"Present PR list" [shape=box];
"User selects PRs" [shape=box];
"Prepare repo access" [shape=box];
"Pre-fetch branches" [shape=box];
"Fetch existing threads" [shape=box];
"Spawn review agents" [shape=box];
"Process next PR result" [shape=box];
"Present findings + ask action" [shape=box];
"User choice?" [shape=diamond];
"Generate fixes in worktree" [shape=box];
"Present patches + ask approval" [shape=box];
"Post comments to ADO" [shape=box];
"Set vote" [shape=box];
"Save session" [shape=box];
"Cleanup per-PR" [shape=box];
"More PRs?" [shape=diamond];
"Print aggregate summary + cleanup" [shape=doublecircle];
"No active PRs" [shape=doublecircle];
"Parse input" -> "Input type?";
"Input type?" -> "Delegate to dx-pr-review" [label="PR URL"];
"Input type?" -> "Load MCP tools + resolve repo" [label="repo URL or empty"];
"Load MCP tools + resolve repo" -> "List active PRs";
"List active PRs" -> "PRs found?";
"PRs found?" -> "Present PR list" [label="yes"];
"PRs found?" -> "No active PRs" [label="no"];
"Present PR list" -> "User selects PRs";
"User selects PRs" -> "Prepare repo access";
"Prepare repo access" -> "Pre-fetch branches";
"Pre-fetch branches" -> "Fetch existing threads";
"Fetch existing threads" -> "Spawn review agents";
"Spawn review agents" -> "Process next PR result";
"Process next PR result" -> "Present findings + ask action";
"Present findings + ask action" -> "User choice?";
"User choice?" -> "Generate fixes in worktree" [label="post with patches"];
"User choice?" -> "Post comments to ADO" [label="post comments only"];
"User choice?" -> "Present findings + ask action" [label="edit"];
"User choice?" -> "Cleanup per-PR" [label="cancel"];
"Generate fixes in worktree" -> "Present patches + ask approval";
"Present patches + ask approval" -> "Post comments to ADO" [label="approved"];
"Present patches + ask approval" -> "Post comments to ADO" [label="cancel patches"];
"Post comments to ADO" -> "Set vote";
"Set vote" -> "Save session";
"Save session" -> "Cleanup per-PR";
"Cleanup per-PR" -> "More PRs?";
"More PRs?" -> "Process next PR result" [label="yes"];
"More PRs?" -> "Print aggregate summary + cleanup" [label="no"];
}
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.
- 19d ago Changed · +6 lines 93837475fe51
- 1mo ago Changed e7d745a863a6
- 1mo ago First seen · 608 lines · 32 tokens per session scan C 41e45d4bbe20
dx-pr-review-all is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 5,957 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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…