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 HigorAlves/orc --skill pr-size-budgetgit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/higoralves/orc/pr-size-budget)<a href="https://agentmods.dev/skills/higoralves/orc/pr-size-budget"><img src="https://agentmods.dev/badge/skills/higoralves/orc/pr-size-budget/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/higoralves/orc/pr-size-budget"><img src="https://agentmods.dev/badge/skills/higoralves/orc/pr-size-budget.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.00042 | $0.01634 |
| Opus 5.5 | $0.00017 | $0.00654 |
| Sonnet 5.5 | $0.00008 | $0.00327 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
pr-size-budget 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 7d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR size budget
Overview
Big PRs starve review quality. orc enforces a soft iron rule at PR-creation time: the diff (additions + deletions, post-exclusion) is computed against the base branch and compared to a budget. When over budget, the user picks one of three paths — never silently ignored, never hard-blocked.
This skill is the single source of truth. /orc:ship, /orc:flow, and /orc:stack-pr all call the orc-pr-size CLI (plugin bin/, on PATH while orc is enabled) and present the gate prompt defined here. If you're tempted to reimplement LOC math or the prompt elsewhere — don't.
Announce at start: "I'm using the pr-size-budget skill because this command opens or sizes a PR."
Budget resolution order
Highest precedence wins:
- CLI flag —
--max-loc <N>on/orc:ship,/orc:flow,/orc:stack-pr. - Environment —
$ORC_PR_LOC_BUDGET(per-shop default, e.g. set in shell init). - Per-repo config —
<repo_root>/.orc/pr-budget.json#budget. - Plugin setting — userConfig
pr_size_budget(prompted at plugin enable; exported asCLAUDE_PLUGIN_OPTION_PR_SIZE_BUDGET). Per-repo intent deliberately beats this per-user default. - Built-in default —
300.
--no-size-gate bypasses the gate entirely (records nothing in the PR body). Use sparingly — typically only for emergency fixes where review-cycle time is the dominant cost.
What counts toward the budget
additions + deletions of the diff base...HEAD (three-dot, the symmetric-difference form gh pr create uses), after applying the exclusion pathspecs. Modified lines count as 1 add + 1 del = 2 LOC — same as git diff --shortstat reports.
Default exclusion globs
These never count:
- Lockfiles —
package-lock.json,pnpm-lock.yaml,yarn.lock,Cargo.lock,go.sum,Gemfile.lock,composer.lock,poetry.lock,uv.lock, any*.lock/*.lockb. - Snapshots / generated —
**/__snapshots__/**,**/__generated__/**,**/generated/**,**/*.gen.{ts,go},**/*.pb.{go,ts},**/*_pb2.py. - Build artifacts —
**/dist/**,**/build/**,**/.next/**. - Generated browser-QA proof —
e2e/specs/**,e2e/tests/**(Playwright plans + tests written by/orc:qa's planner/generator; reviewers see them, the budget doesn't count them).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago Changed · -47 lines d2e23c40b090
- 20d ago Changed · +1 lines 5943f00c50d8
- 22d ago Changed 5ddefa0b426a
- 1mo ago First seen · 158 lines · 42 tokens per session scan A a011891df843
pr-size-budget is a skill published in the GitHub repository HigorAlves/orc (7 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,634 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-09-03.
Other skills, from other repositories
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
commit
Generate a conventional commit message for staged changes.
commit
Changelog and commit — lightweight motion for day-to-day plugin dev work in the monorepo. One commit per plugin scope; CHANGELOG and staging routed by detected slug. Trigger when the user says "commit", "commit this", "save this", "wrap this up", "let's commit", or finishes a change and wants to capture it. NOT for…
atlas-changelog
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".