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 aeonfun/aeon --skill pr-triagegit clone --depth 1 https://github.com/aeonfun/aeonWrote 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/aeonfun/aeon/pr-triage)<a href="https://agentmods.dev/skills/aeonfun/aeon/pr-triage"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/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/aeonfun/aeon/pr-triage"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/pr-triage.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.00026 | $0.03468 |
| Opus 5.5 | $0.00010 | $0.01387 |
| Sonnet 5.5 | $0.00005 | $0.00694 |
| Haiku 4.5 | $0.00003 | $0.00347 |
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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pr-triage — 100% identical, 2 lines differ
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
- aeonfun/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.
- 6d ago Changed 18bb56adb6f7
- 21d ago Changed edf8d971ecdb
- 1mo ago First seen · 253 lines · 26 tokens per session scan A 03d8f0348ff5
pr-triage is a skill published in the GitHub repository aeonfun/aeon (782 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 3,468 once invoked, about $0.0001 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-05.
Other skills, from other repositories
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
pr-description
Write or update a GitHub PR description a teammate understands in one quick read: a picture when one fits, then a few plain sentences grounded in the diff and real verification. Use when opening a PR or editing its description.
pr-creator
Create well-structured pull requests with proper descriptions and labels.
nox-review
Run an adversarial review of a code diff or a plan artifact under a second AI harness, headlessly, from an ephemeral git worktree with the repository's own instruction, hook and credential files removed. Use when a change needs a reviewer that did not write it, when a cross-model second opinion is wanted before…
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.