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 agentmods add commands/everyinc/compound-engineering-plugin/triage-prsgit clone --depth 1 https://github.com/EveryInc/compound-engineering-pluginWhat 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 | $0.00024 | $0.01620 |
| Opus 5 | $0.00012 | $0.00810 |
| Sonnet 5 | $0.00005 | $0.00324 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
triage-prs 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 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.
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
4 near-identical copies found in the catalogue:
- triage-prs — 100% identical, 0 lines differ
- triage-prs — 100% identical, 0 lines differ
- triage-prs — 100% identical, 2 lines differ
- triage-prs — 91% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Open Pull Requests
Review, label, and act on all open PRs for a repository using parallel review agents. Produces a grouped triage report, applies labels, cross-references with issues, and walks through each PR for merge/comment decisions.
Step 0: Detect Repository
Detect repo context:
- Current repo: !
gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "no repo detected" - Current branch: !
git branch --show-current 2>/dev/null
If $ARGUMENTS contains a GitHub URL or owner/repo, use that instead. Confirm the repo with the user if ambiguous.
Step 1: Gather Context (Parallel)
Run these in parallel:
-
List all open PRs:
gh pr list --repo OWNER/REPO --state open --limit 50 -
List all open issues:
gh issue list --repo OWNER/REPO --state open --limit 50 -
List existing labels:
gh label list --repo OWNER/REPO --limit 50 -
Check recent merges (to detect duplicate/superseded PRs):
git log --oneline -20 main
Step 2: Batch PRs by Theme
Group PRs into review batches of 4-6 based on apparent type:
- Bug fixes - titles with
fix,bug, error descriptions - Features - titles with
feat,add, new functionality - Documentation - titles with
docs,readme, terminology - Configuration/Setup - titles with
config,setup,install - Stale/Old - PRs older than 30 days
Step 3: Parallel Review (Team of Agents)
Spawn one review agent per batch using the Task tool. Each agent should:
For each PR in their batch:
- Run
gh pr view --repo OWNER/REPO <number> --json title,body,files,additions,deletions,author,createdAt - Run
gh pr diff --repo OWNER/REPO <number>(pipe tohead -200for large diffs) - Determine:
- Description: 1-2 sentence summary of the change
- Label: Which existing repo label fits best
- Action: merge / request changes / close / needs discussion
- Related PRs: Any PRs in this or other batches that touch the same files or feature
- Quality notes: Code quality, test coverage, staleness concerns
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 First seen · 194 lines · 24 tokens per session scan A 3b41fcab5d4c
triage-prs is a command published in the GitHub repository EveryInc/compound-engineering-plugin (24,696 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 1,620 once invoked, about $0.0001 per session on Opus 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-08-30.
Other commands, from other repositories
specify
Create or update the feature specification from a natural language feature description.
constitution
Create or update the project constitution from interactive or provided principle inputs.
speckit.assess.research
Gather evidence — users, market, prior art, and data — to support or challenge the idea.
plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.