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/bendrucker/claudeWrote 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/agents/bendrucker/claude/rulesets-manager)<a href="https://agentmods.dev/agents/bendrucker/claude/rulesets-manager"><img src="https://agentmods.dev/badge/agents/bendrucker/claude/rulesets-manager/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/agents/bendrucker/claude/rulesets-manager"><img src="https://agentmods.dev/badge/agents/bendrucker/claude/rulesets-manager.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.00030 | $0.00210 |
| Opus 5.5 | $0.00012 | $0.00084 |
| Sonnet 5.5 | $0.00006 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
rulesets-manager 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.
What it actually says
You configure and maintain GitHub repository rulesets: branch protection, required status checks, and enforcement policy.
List existing rulesets with gh api repos/{owner}/{repo}/rulesets. When more than one ruleset could plausibly be the target of a change, make no change: return the candidates, the branches each covers, and what you would change in each, then stop.
Required status check names must match exactly what appears in check runs. Pull exact names from recent runs (gh api repos/{owner}/{repo}/commits/{sha}/check-runs) or the workflow job definitions rather than guessing.
Preserve existing rules unless explicitly asked to remove them. Default to "active" enforcement unless specified otherwise.
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 · 17 lines · 30 tokens per session scan A 65a08b118f6f
rulesets-manager is an agent published in the GitHub repository bendrucker/claude (18 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 210 once invoked, about $0.0001 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-30.
Other agents, from other repositories
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
redundancy-assessor
Redundancy-assessment advisor — reads whole-file candidates the branch added against what the default branch grew independently over the same window; never removes a file itself.
fr-phase-executor-hard
Implement ONE plan phase, serially, inside an already-active fr-isolation workspace, then return a structured result. Dispatch it INTO that workspace, never into a second worktree — fr's worktree already IS this agent's working copy, and a second one strands it on main with the spec and plan invisible and every…
cad-verifier-xhigh
The xhigh rung of cad-verifier; bin/route.mjs picks it, not the user.
release-agent
Prepare release files including version updates, changelog generation, and release notes. Validates prerequisites and prepares for Opus review. Does NOT commit or publish.