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-reviews-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-reviews-report)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-pr-reviews-report"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-pr-reviews-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-reviews-report"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-pr-reviews-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.00059 | $0.04257 |
| Opus 5.5 | $0.00024 | $0.01703 |
| Sonnet 5.5 | $0.00012 | $0.00851 |
| Haiku 4.5 | $0.00006 | $0.00426 |
Grade A, and why
dx-pr-reviews-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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You generate review reports for multiple pull requests. By default, lists PRs where the current user is a reviewer (excluding own PRs) and processes them in parallel. With --any, lists all PRs with review threads without filtering and processes sequentially with user selection.
Modes
| Mode | Filter | Processing | User Prompt |
|---|---|---|---|
| Mine (default) | i_am_reviewer: true, exclude own PRs |
Parallel (all at once) | No — auto-generates all |
Any (--any flag) |
All PRs with review threads, no author filter | Sequential with selection | Yes — user picks which PRs |
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 - Confluence space (Jira): read from
.ai/config.yamlconfluence.space-key - Confluence PR review root (Jira): read from
.ai/config.yamlconfluence.pr-review-root
1. Parse Input
Parse $ARGUMENTS to determine the mode:
Flag detection
If $ARGUMENTS contains --any, remove it from the arguments and set MODE=any. Otherwise MODE=mine.
Remaining arguments
| Input | Mode | Example |
|---|---|---|
| (empty) | Current repo, default count | /dx-pr-reviews-report (mine, 5 PRs) |
<number> |
Current repo, N PRs | /dx-pr-reviews-report 5 |
--any |
Current repo, any mode, 10 PRs | /dx-pr-reviews-report --any |
--any <number> |
Current repo, any mode, N PRs | /dx-pr-reviews-report --any 20 |
<repo URL> |
That repo, default count | /dx-pr-reviews-report https://{org}/_git/My-Repo |
<repo URL> <number> |
That repo, N PRs | /dx-pr-reviews-report https://{org}/_git/My-Repo 20 |
<PR URL> |
Single PR (delegate) | /dx-pr-reviews-report https://.../_git/.../pullrequest/12345 |
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 46136fc01bc1
- 19d ago Changed · +5 lines a3b2e671f39e
- 1mo ago Changed e64b986305cb
- 1mo ago First seen · 354 lines · 59 tokens per session scan A 6702c0f73e32
dx-pr-reviews-report is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 4,257 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…