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 jrgilbertson/the-rookery --skill checking-pr-readinessgit clone --depth 1 https://github.com/jrgilbertson/the-rookeryWrote 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/jrgilbertson/the-rookery/checking-pr-readiness)<a href="https://agentmods.dev/skills/jrgilbertson/the-rookery/checking-pr-readiness"><img src="https://agentmods.dev/badge/skills/jrgilbertson/the-rookery/checking-pr-readiness/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/jrgilbertson/the-rookery/checking-pr-readiness"><img src="https://agentmods.dev/badge/skills/jrgilbertson/the-rookery/checking-pr-readiness.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.00100 | $0.05411 |
| Opus 5 | $0.00050 | $0.02705 |
| Sonnet 5 | $0.00020 | $0.01082 |
| Haiku 4.5 | $0.00010 | $0.00541 |
Grade A, and why
checking-pr-readiness 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 today.
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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checking PR Readiness
Check whether a branch is ready to enter the pull request and continuous-integration process. Internally the gate gathers the full working surface, upstream-step receipts, plan-versus-delivered, pre-PR review checks, and learning signal. Then brief a recommendation plus numbered live options and wait for a numbered reply from whoever is talking.
The gate is read-only. Companion skills own edits, reviews, and capture; the host repository's hooks and task runners own deterministic re-runs. This skill verifies those from receipts or dispatches the skill that owns them. Nothing is done without evidence in the captured gather. Incomplete gather cannot offer Approve.
Status words
Every check reports with one word from this closed set, used consistently and without synonyms:
- verified — a named receipt supports the claim in the captured gather, or, for solution simplicity only, this gate's own live fresh dispatch against an unchanged subject does.
- attested — the owner states missing intent (step 4) and no durable source exists; recorded as attestation, not as evidence. Do not use this word to vouch that a missing review or simplify step happened.
- not verified — no receipt exists and no attestation was given.
Also in the set (same one-token rule): failed, not run, skipped, unavailable, bypassed, not applicable. Use the ordinary meaning of each word; bypassed always records the owner's reason.
Workflow
Bind identity first. Read
references/identity-and-argv.md when capturing
the native subject, full head, target/base ref, and full base OID, when
proving helper --base binding, when rerunning a repository-authored check,
and immediately before accepting option 1.
1. Gather the working surface
The finishing path will stage this surface. Create an owner-only mktemp -d
directory outside the target repository first; capture helper stdout there and
do not echo the inventory into chat. Do not remove that directory while the
run is waiting for a numbered reply. Run
scripts/surface-report.sh when it is present and
executable. Pass --full so the listing written to temp includes every path.
The same run supplies step 6's informational size diagnostics; optional
--cap values and their interpretation live in
references/sweep-classes.md class 11. Always
produce the surface report on this run (omit --defer even when a repository
gate owns a size check).
What ships with it
7 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.
- today Changed · +2 lines 27b5200e07f6
- yesterday Changed · +1 lines 45dc49fc7291
- 2d ago Changed · +26 lines e0faf28ad7d5
- 3d ago Changed · -2 lines 98fadc81a2d4
- 4d ago Changed · +3 lines 2685ca9a76c8
- 6d ago Changed · +20 lines · -39 tokens per session 01e93f749c33
- 11d ago First seen · 392 lines · 139 tokens per session scan A 70d67980c7a0
checking-pr-readiness is a skill published in the GitHub repository jrgilbertson/the-rookery (4 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 5,411 once invoked, about $0.0005 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-31.
Other skills, from other repositories
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-pr-comments
Resolve inline code review comments on a GitHub PR. Use when asked to "resolve review comments", "address PR feedback", "fix PR comments", or "work through review comments". Fetches every inline comment with its surrounding code context, then applies each change systematically.
chained-pr
Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.