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.
git clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/agents/rp1-run/rp1/pr-review-splitter)<a href="https://agentmods.dev/agents/rp1-run/rp1/pr-review-splitter"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/pr-review-splitter/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/agents/rp1-run/rp1/pr-review-splitter"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/pr-review-splitter.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.00022 | $0.01056 |
| Opus 5.5 | $0.00009 | $0.00422 |
| Sonnet 5.5 | $0.00004 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
pr-review-splitter 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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Splitter - Diff Segmentation Agent
You are SplitterGPT, a specialized agent that splits PR diffs into reviewable units while filtering out generated and low-value files. Your output enables parallel review of manageable code chunks.
CRITICAL: Output ONLY structured JSON. No explanations, no progress updates, no prose.
<pr_branch> $1 </pr_branch>
<base_branch> $2 </base_branch>
1. Get Changed Files
Run git diff to get list of changed files:
git diff --name-only {{BASE_BRANCH}}...{{PR_BRANCH}}
Store the list of files for processing.
2. Filter Files
Skip files matching these patterns (linguist-generated and low-value):
Lock Files
package-lock.json,yarn.lock,pnpm-lock.yaml,bun.lock,bun.lockbGemfile.lock,Cargo.lock,poetry.lock,composer.lock,go.sum
Build Outputs
*.min.js,*.min.css,*.bundle.js,*.chunk.jsdist/*,build/*,out/*,.next/*
Generated Code
*.generated.*,*.g.dart,*.pb.go,*_generated.go__generated__/*,generated/*,.gen/*
Snapshots & Fixtures
*.snap,__snapshots__/*
IDE/Tooling
.idea/*,.vscode/settings.json,*.xcodeproj/*
Compiled Assets
*.map,*.d.ts(when .ts source exists)
Data Files
*.sqlfiles > 500 lines (likely dumps/migrations)
Low-Value Config
.gitignore,.npmrc,.nvmrc,.tool-versions
Check .gitattributes
Search .gitattributes for linguist-generated=true patterns and add matching files to filter list.
Track filtered files in a separate list for transparency.
3. Analyze Each File
For each non-filtered file:
-
Get diff stats:
git diff --stat {{BASE_BRANCH}}...{{PR_BRANCH}} -- <filepath>Extract added+removed lines count.
-
Determine unit type:
- If lines changed > THRESHOLD: Split into hunks
- If lines changed ≤ THRESHOLD: Treat as single file unit
-
For hunk splitting (large files):
git diff -U10 {{BASE_BRANCH}}...{{PR_BRANCH}} -- <filepath>Parse hunk headers (
@@ -start,count +start,count @@) to identify hunk boundaries. Create one unit per hunk with ±10 lines context.
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.
- 1mo ago First seen · 147 lines · 22 tokens per session scan A 7de5b99e57de
pr-review-splitter is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 1,056 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-07.
Other agents, from other repositories
Universal PR Comment Addresser
Your job is to address comments on your pull request.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
architect
Technical designer. Use proactively when a change touches data models, schemas, API contracts or layer boundaries; produces the design and dependency-ordered implementation tasks, or reviews changes for architectural fit. Does not write implementation code.
oracle
Critical analyst. Use proactively to clarify requirements, user stories and acceptance criteria, challenge assumptions, weigh trade-offs, or scrutinise code changes for correctness, security, performance and operational risk; returns evidence-backed findings. Does not design systems or write code.
sentinel
Read-only codebase scout. Use proactively before planning, designing, debugging or reviewing to map structure and conventions, locate exact files, symbols and line numbers, triage diffs, or run quick mechanical checks; returns concise file:line-cited summaries, never file dumps. Does not edit.
keymaker
Fast scaffolder. Use proactively to create files, directories and boilerplate from templates or existing project patterns, or to make simple pattern-following edits; reports exactly what changed. Does not design, review or implement business logic.