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 aaronjmars/aeon-agent --skill pr-triagegit clone --depth 1 https://github.com/aaronjmars/aeon-agentWrote 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-triage)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/pr-triage"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/pr-triage/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-triage"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/pr-triage.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.00026 | $0.03384 |
| Opus 5 | $0.00013 | $0.01692 |
| Sonnet 5 | $0.00005 | $0.00677 |
| Haiku 4.5 | $0.00003 | $0.00338 |
Grade A, and why
pr-triage 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 3d 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.
This is a copy
100% identical to pr-triage — 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — PR scope. Accepts
owner/repo,owner/repo#N, or empty (all watched repos). If empty, scans every repo inmemory/watched-repos.md.
External PRs that sit unanswered look unwelcoming. This skill is the first touch for every external pull request — it reads the diff, applies a structured rubric, posts a comment with a verdict + rationale, and labels the PR so a human reviewer can pick it up with full context. It is not a substitute for pr-review (depth) or auto-merge (execution); it is the welcoming layer that runs before either of those decide whether to engage.
What "external" means
Any PR whose author is not in the trusted set qualifies. The trusted set is, by precedence:
- Logins ending in
[bot](dependabot[bot],renovate[bot],github-actions[bot], …) — these route toauto-merge/pr-review. - The agent's own login:
aeonframework,aeonfun, and any login under a## Trusted Authorsheading inmemory/watched-repos.md(same allowlist convention used byauto-merge).
Everything else is external and gets triaged.
Config
memory/watched-repos.md:
# Watched Repos
- aeonfun/aeon
- aaronjmars/aeon-agent
## Trusted Authors
- alice
- bob
If the file is missing and ${var} is empty, log PR_TRIAGE_OK no-watched-repos and exit.
Read memory/MEMORY.md for context.
Read memory/triaged-prs.json (if present; else treat as {}) — schema: {"owner/repo": [{"n": 143, "sha": "abc123", "at": "2026-04-29", "verdict": "ACCEPTED"}, ...]}. Used for idempotency keyed on (PR number, headRefOid).
Read the last 2 days of memory/logs/ as a fallback dedup signal in case the JSON state file is missing.
Steps
1. Resolve targets
${var}matches^[\w.-]+/[\w.-]+#\d+$→ single-PR mode: target that exact PR.${var}matches^[\w.-]+/[\w.-]+$→ repo mode: scan all open PRs on that one repo.${var}is set but matches neither shape → abort withpr-triage: invalid var — expected owner/repo or owner/repo#Nand exit.${var}is empty → fleet mode: read non-comment, non-blank-lines frommemory/watched-repos.md(everything above the## Trusted Authorsheading).
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.
- 3d ago First seen · 253 lines · 26 tokens per session scan A 03d8f0348ff5
pr-triage is a skill published in the GitHub repository aaronjmars/aeon-agent (11 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 3,384 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pr-triage, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.