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 Knuckles-Team/repository-manager --skill repository-manager-fleet-scale-operationsgit clone --depth 1 https://github.com/Knuckles-Team/repository-managerWrote 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/knuckles-team/repository-manager/repository-manager-fleet-scale-operations)<a href="https://agentmods.dev/skills/knuckles-team/repository-manager/repository-manager-fleet-scale-operations"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-fleet-scale-operations/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/knuckles-team/repository-manager/repository-manager-fleet-scale-operations"><img src="https://agentmods.dev/badge/skills/knuckles-team/repository-manager/repository-manager-fleet-scale-operations.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.00141 | $0.02205 |
| Opus 5 | $0.00071 | $0.01103 |
| Sonnet 5 | $0.00028 | $0.00441 |
| Haiku 4.5 | $0.00014 | $0.00220 |
Grade A, and why
repository-manager-fleet-scale-operations 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 10d 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.
Repository Manager — Fleet-Scale Operations
Operating ~234 repositories with dozens of concurrent lanes. The failure modes at
this scale are different in kind from a single lane's: you do not lose work to a
merge conflict, you lose it to a machine that ran out of memory during a git add, or to a mass prune that deleted a branch someone was still holding.
When to use
- Launching a wave of lanes across several repositories.
- Reclaiming accumulated worktrees and branches.
- Draining more than one repository's merge queue.
- Deciding how many heavy jobs may run concurrently.
When NOT to use
- One lane's lifecycle →
repository-manager-lane-lifecycle. - Landing/reconciling one branch →
repository-manager-merge-and-reconcile.
★ The binding constraint is disk I/O and swap — not the agent cap
The instinct is to size a wave by how many agents you may run. That is the wrong
resource. Measured at peak on this host: load ~26 on 24 cores, swap 100%
exhausted, 14 concurrent uv sync against a 112 GB cache — and a plain
git add died with Bus error. That is data loss caused by scheduling, not by
any lane doing anything wrong.
Cap HEAVY lanes at ~3–4 concurrently, independent of total lane count. Heavy means anything that does bulk I/O or bulk compilation:
| Heavy (cap 3–4) | Light (costs almost nothing) |
|---|---|
uv sync / any dependency resolution |
editing files |
cargo build / cargo check |
reading, searching, KG queries |
pre-commit run --all-files |
git commit, git status |
a full pytest sweep |
--lane doctor, --merge-queue status |
| container image builds | writing docs/skills |
Light lanes are nearly free; run as many as you have work for. The mistake is treating all lanes as equivalent and sizing the whole wave by the heaviest one — or worse, by the agent cap, which measures nothing physical.
Two corollaries:
- Serialize the LEASE-class heavies.
uv sync/uv lock,pre-commit --all-files, and any venv swap are already LEASE-class because of this. Run them through the lease and let contenders defer:agent-utilities lane lease --resource dependency-lock --operation relock -- uv lock. Exit 75 = another lane holds it. - Prune build artifacts at verify time, not at the end. A shared cargo target
dir has already hit
ENOSPCmid-wave. Each lane builds into./target-isolatedand removes it when its gate is green.
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.
- 10d ago First seen · 195 lines · 141 tokens per session scan A 3b81bd07ac20
repository-manager-fleet-scale-operations is a skill published in the GitHub repository Knuckles-Team/repository-manager (2 stars, last pushed 13d ago), licensed MIT. It adds 141 tokens to every session and 2,205 once invoked, about $0.0007 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
status
Show a comprehensive project status dashboard: task queue, blocked items, session state, verification, and git status.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.
openclaw-github-repo-commander
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis.
metagit-projects
Ongoing workspace and project management for OpenClaw and Hermes agents. Use when starting work, organizing repos, or before creating a new project folder so existing metagit projects are reused instead of duplicated.
metagit-rewrite-campaign
Orchestrate a reference-implementation rewrite across source and target repos using campaigns, parity registry conventions, objectives, and subagent handoffs.
metagit-control-center
Use when running metagit as an MCP control center for multi-repo awareness, guarded sync, and operational knowledge across ongoing agent tasks.