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 repo-gardenergit 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/repo-gardener)<a href="https://agentmods.dev/skills/jrgilbertson/the-rookery/repo-gardener"><img src="https://agentmods.dev/badge/skills/jrgilbertson/the-rookery/repo-gardener/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/repo-gardener"><img src="https://agentmods.dev/badge/skills/jrgilbertson/the-rookery/repo-gardener.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.00088 | $0.02785 |
| Opus 5.5 | $0.00035 | $0.01114 |
| Sonnet 5.5 | $0.00018 | $0.00557 |
| Haiku 4.5 | $0.00009 | $0.00279 |
Grade A, and why
repo-gardener 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 13d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Gardener
Start only when the request names repo-gardener, its /repo-gardener or $repo-gardener form, the repository gardening automation, or the nightly gardener. Treat a request about maintenance, CI, repository health, trackers, issues, or overnight work that names none of these as not this skill.
Sense one repository, dispatch Executors that each ship one reviewable PR, and post one morning report. Run as Coordinator plus Executors. As Coordinator, sense, select, dispatch, and report. Never implement, push, or merge as Coordinator. Give each Executor one worktree, one branch, and one unmerged PR. Use Scouts for read-only evidence. Each Executor verifies its unit, publishes through Compound Engineering, and reports babysit's result. Keep CI as the merge gate. Leave merge to a human. Treat a run that authors nothing but reports as a complete run.
Read the policy
Read .agents/repo-gardener.yaml on the refreshed default branch once at
the start. If the default branch cannot be refreshed, read the last
fetched local copy of the default branch and name that in the report.
Never read the policy from a topic branch or a dirty checkout; without a
default-branch copy, run sense-only. Treat that file as the only durable
policy. Read protected_paths as globs an Executor never
writes. Treat the policy file itself as always
protected. Read max_pull_requests as the number of pull requests one
run may open, one Executor each, with 0 meaning sense and report only.
Read scans as a list of argv lists, each
one process run from the repository root. Read verify as the argv lists
the owner approves for an Executor to verify its unit, each run from the
worktree root; this is the exact caller-approved verification command argv
list it must pass before publication. An empty list means no PR opens. Read
optional report_issue as a GitHub issue number that receives one report
comment per run.
Treat a missing or unreadable file as a sense-only run. Put a proposed
complete policy file in that report for the owner to commit. Start from
the bundled policy template. Fill scans
with whole-project scans nothing else runs on a schedule, and verify
with the smallest gating subset CI runs on pull requests, never a
watch-mode command. Do not validate the file with a script. Treat a
readable file in which protected_paths, max_pull_requests, scans,
or verify is missing, misspelled, repeated as a duplicate top-level
key, or not of its expected type as unreadable: run sense-only and name
that field in the report.
What ships with it
1 file 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.
- 13d ago Changed · -15 lines 66f90a9c8ab1
- 17d ago Changed · +2 lines 2d4cfbb19d61
- 23d ago Changed · +2 lines 8c60c54489fd
- 1mo ago Changed bcc0d350f029
- 1mo ago Changed · +106 lines · +17 tokens per session dfa54c132550
- 1mo ago Changed · -2 lines 83a8eb646258
- 1mo ago Changed · -2 lines · -29 tokens per session 287501229bc3
- 1mo ago Changed · -6 lines · -8 tokens per session a0865131df2e
- 1mo ago Changed · -241 lines · -16 tokens per session 165293aefa6e
- 1mo ago First seen · 374 lines · 124 tokens per session scan A d57b5d176013
repo-gardener is a skill published in the GitHub repository jrgilbertson/the-rookery (12 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 2,785 once invoked, about $0.0004 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-31.
Other skills, from other repositories
chief-customer-officer-advisor
Chief Customer Officer advisory for startups: retention decomposition (gross retention vs NRR honesty, churn root-cause taxonomy), customer segmentation strategy (differential investment across tiers + ICP fit scoring), CS team coverage model (pooled vs named CSM thresholds + ratio math), and CS team org evolution (CS…
agentflow
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution.
chief-of-staff
C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right…
event-staffing-ordering
Order W-2 compliant temporary event staff for conventions, trade shows, festivals, concerts, sporting events, and brand activations across 300+ US and Canadian markets via TempGuru. Covers city coverage, role pricing, availability, state compliance lookups via MCP, and request submission.
acceptance-orchestrator
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
cro-review
/cs:cro-review — Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time. Use when the forecast misses pipeline coverage, win rates drop, or before scaling the sales team.