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/CBirkbeck/mathlib-qualityWrote 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/commands/cbirkbeck/mathlib-quality/taupr)<a href="https://agentmods.dev/commands/cbirkbeck/mathlib-quality/taupr"><img src="https://agentmods.dev/badge/commands/cbirkbeck/mathlib-quality/taupr/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/commands/cbirkbeck/mathlib-quality/taupr"><img src="https://agentmods.dev/badge/commands/cbirkbeck/mathlib-quality/taupr.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.00000 | $0.04353 |
| Opus 5.5 | $0.00000 | $0.01741 |
| Sonnet 5.5 | $0.00000 | $0.00871 |
| Haiku 4.5 | $0.00000 | $0.00435 |
Grade A, and why
taupr 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 — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/taupr — the Tau Ceti worker loop
Modelled on the reference worker (kim-em/TauCetiWorker): a round does exactly one unit
of work — the first of these that applies.
R1 REBASE one of our PRs has a genuine TauCeti/ conflict after a sibling merged
R2 FIX-CI one of our PRs has `build` red — it cannot be reviewed until it builds
R3 FIX one of our PRs has findings: fix the code, or contest a wrong one in-thread
R4 REVIEW one of our PRs is green but CI has not reviewed it for ≥ 1h → --post
R5 AUTHOR otherwise: open a new PR advancing a target — ONLY if fewer than
--max-open (default 3) of our PRs are already open, else IDLE
Maintenance outranks authoring. R1–R4 come first so PRs already in flight cannot be starved by opening yet more of them. A round that finds work at R2 stops there.
R5 is capped at 3 of our own PRs open. This matters more than it looks. A PR that is still building is not red, has no findings, and is not yet reviewable — so no step catches it, the board reads as quiet, and an uncapped round falls through to authoring. On a ten-minute loop that is a new PR every tick. Worse, R4's one-hour wait means a green PR looks like nothing to do for a whole hour, which is exactly when the loop would be busiest authoring.
So: if 3 or more of our PRs are open, R5 does not run and the round reports IDLE.
Idle is a correct outcome — it means the work in flight is waiting on someone else. Change
it with --max-open <n>; --max-open 0 lifts the cap.
Count PRs we authored that are still open, in any state. Merged and closed do not count, so the cap self-releases as work lands.
CI reviews our PRs; we do not race it. Opening the PR is enough — pr-build runs, and
a green build triggers the review automatically. Self-reviewing costs your subscription and
your wall-clock, so R4 exists only as a fallback for PRs CI has left sitting.
Merging, closing and de-duplicating are the repo's CI, not this loop. Do not merge green PRs, close stuck ones, or sweep duplicates from here.
A GitHub API failure aborts the round. It must never read as "nothing to do" and fall through to R5 — a transient outage would then author duplicate PRs. No data means stop, not proceed.
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 · 369 lines · 0 tokens per session scan A be725e683e42
taupr is a command published in the GitHub repository CBirkbeck/mathlib-quality (35 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,353 tokens. 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 commands, from other repositories
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
land
Resolve and squash merge one named, currently authorized pull request.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.
ship
Deliver one goal end to end (clarify, implement, PR, review, CI, merge) via the ship skill.