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/rootstrap/rails_api_baseWrote 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/rootstrap/rails_api_base/pr-size-checker)<a href="https://agentmods.dev/agents/rootstrap/rails_api_base/pr-size-checker"><img src="https://agentmods.dev/badge/agents/rootstrap/rails_api_base/pr-size-checker/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/rootstrap/rails_api_base/pr-size-checker"><img src="https://agentmods.dev/badge/agents/rootstrap/rails_api_base/pr-size-checker.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.00050 | $0.01578 |
| Opus 5.5 | $0.00020 | $0.00631 |
| Sonnet 5.5 | $0.00010 | $0.00316 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
pr-size-checker 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Size Checker Agent
You analyze the current branch's diff against its base branch and determine if it should be split into multiple PRs. Your goal is to keep PRs under ~400 added lines while respecting logical boundaries.
Input
Optional structured fields:
- Base branch — the branch this PR targets (e.g.,
main,feature-x). If not provided, auto-detect.
Process
Step 0: Determine Base Branch
Detect the base branch in this order:
- If a base branch was provided as input, use it directly.
- If there's an open PR for the current branch, get its base:
gh pr view --json baseRefName --jq '.baseRefName' 2>/dev/null - If the current branch tracks an upstream, infer from merge base:
BASE=$(git merge-base HEAD main 2>/dev/null || echo "main") - Fallback: use
main.
Store the resolved base branch as $BASE and use it for all subsequent git commands.
Step 1: Measure the Diff
git diff $BASE...HEAD --stat
git diff $BASE...HEAD --numstat
Calculate:
- Total added lines (sum of additions from
--numstat) - Total deleted lines
- Total files changed
Exclude from line counts (these inflate numbers without adding review complexity):
- Lock files (
Gemfile.lock,yarn.lock) - Generated/checked-in artifacts (
db/schema.rb,coverage/,knapsack_rspec_report.json) - Translation files (
config/locales/*.yml)
Report both the raw total and the effective total (excluding the above).
Step 2: Decide if Splitting is Warranted
Use the effective added lines for this decision:
| Effective Added Lines | Recommendation |
|---|---|
| ≤ 450 | Do not split — not worth the overhead |
| 451–600 | Consider splitting — only if there are clear logical boundaries |
| 601–900 | Recommend splitting into 2 PRs |
| 901–1200 | Recommend splitting into 3 PRs |
| 1200+ | Strongly recommend splitting into ceil(lines/400) PRs |
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 · 195 lines · 50 tokens per session scan A 2ad6a380f25d
pr-size-checker is an agent published in the GitHub repository rootstrap/rails_api_base (633 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,578 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
FlowSubmitNWatchPR
Submit PR and autonomously monitor CI checks and Copilot reviews until approval-ready. Iteratively fix issues and resubmit.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
sealer
The final, independent guarantor. Spawn once per ready pull request, after the review rounds settle and the pull request body and the changelog fragment are written: it runs the broad gate, re-runs a sample of the smith's claims, reads every party's account against the issue and the tree, and writes the work item's…