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/aaronjmars/aeon-agentnpx agentmods add skills/aaronjmars/aeon-agent/pr-reviewWrote 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/aaronjmars/aeon-agent/pr-review)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/pr-review"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/pr-review/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/aaronjmars/aeon-agent/pr-review"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/pr-review.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.00047 | $0.08195 |
| Opus 5 | $0.00023 | $0.04097 |
| Sonnet 5 | $0.00009 | $0.01639 |
| Haiku 4.5 | $0.00005 | $0.00819 |
Grade A, and why
pr-review scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`gh` CLI handles GitHub auth internally — use it over raw `curl`, which would put a bare `$SECRET` on the command line for the Bash permission layer to refuse. Both branches route all outbound GitHub calls through `gh` / This is a copy
89% identical to pr-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Selects the branch and scopes it.
- Default (no
--survey) → per-PR deep review.${var}empty reviews every repo inmemory/watched-repos.md;${var}=owner/reposcopes to one repo;${var}=owner/repo#Nscopes to that exact PR.--survey(aliassurvey) → risk-tiered triage digest (the formerpr-merge). In this branch the remaining tokens follow pr-merge's grammar: passdry-runto skip notify (article + state still write), passowner/repoto override the target repo, combine with a space (--survey dry-run owner/repo). Empty target =aeonfun/aeon.Examples: `` (review every watched repo) ·
owner/repo(review one repo) ·owner/repo#42(review exactly PR 42) ·--survey(triage digest of aeonfun/aeon) ·--survey dry-run(refresh digest, no notify) ·--survey owner/repo(triage a specific repo).
Shared preamble (every run)
Read memory/MEMORY.md for high-level context. Scan the last ~3 days of memory/logs/ for recent activity and to avoid re-reporting the same signal.
Parse ${var} → branch: split ${var} on whitespace.
- If a
--surveyorsurveytoken is present → SURVEY branch (jump to "Survey branch"). Remove that token; the remaining tokens are parsed by the survey branch (dry-run,owner/repooverride, unknown → BAD_VAR). - Otherwise → REVIEW branch (default; continue below). The remaining
${var}is an optionalowner/repoorowner/repo#Nscope (empty = every watched repo).
The two branches never share mutation logic: the REVIEW branch posts PR comments/reviews via gh; the SURVEY branch writes the digest article + state file and (gated) notifies — neither performs an actual gh pr merge. Dispatch to exactly one branch per run.
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.
- yesterday Changed · +19 lines 2389803f54ad
- 4d ago First seen · 445 lines · 47 tokens per session scan A bf3a11650596
pr-review is a skill published in the GitHub repository aaronjmars/aeon-agent (11 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 8,195 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 89% identical to pr-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
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"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…