Borrowing it
Nothing to install: this file belongs to rjwalters/kicad-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rjwalters/kicad-tools/main/.claude/commands/repo/scrub.mdgit clone --depth 1 https://github.com/rjwalters/kicad-toolsWrote 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/rjwalters/kicad-tools/scrub)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/scrub"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/scrub.svg" alt="Measured on agentmods" 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.00033 | $0.04068 |
| Opus 5 | $0.00016 | $0.02034 |
| Sonnet 5 | $0.00007 | $0.00814 |
| Haiku 4.5 | $0.00003 | $0.00407 |
Grade A, and why
scrub 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 3d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/repo:scrub — Public-Surface Scrub
Answer one question the other hygiene commands don't: is there anything here that should not be public?
That gap matters most where agents author content continuously. An agent writing an issue, a runbook, or an incident write-up has no instinct for which identifiers are sensitive, and those artifacts are exactly the genre where account IDs, resource IDs, internal hostnames, and email addresses accumulate. None of it is a credential; all of it is useful to an attacker. The drift is slow and invisible, which is why it needs a check on a routine cadence rather than a person remembering to look.
This command reports. It never edits. Same posture as [[orphans]]: name the file, commit, issue, or PR and the class, and stop. Deleting an issue or rewriting history is irreversible and is an operator decision — and, as the removability section below explains, usually a less complete fix than the operator assumes.
Usage
/repo:scrub # This repo, default verbosity — credentials and live-at-HEAD findings
/repo:scrub --deep # Add history-only and network-topology classes
/repo:scrub --owner <owner> # Every public repo for an owner/org, enumerated from the forge
/repo:scrub --forks # Also sweep the fork network (delegates to repo-scrub-forks.sh)
/repo:scrub --json # Machine-readable findings
/repo:all runs the default form only — this repo, quiet verbosity, no
forge enumeration and no fork sweep. The wide forms cost API calls and minutes,
and belong in a deliberate invocation.
Exit codes
| Code | Meaning |
|---|---|
0 |
Clean — no findings at or above the reporting threshold |
1 |
Findings at HEAD |
2 |
Could not check — no gh, not authenticated, API failure, scan aborted |
History-only findings never set exit 1 on their own. Nearly every repo with
any history has some, none of them fixable without a rewrite nobody is going to
perform, so failing on them means every repo fails forever and the signal is
worth nothing. Code 2 is inconclusive and must never be reported as clean.
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.
- 3d ago First seen · 350 lines · 33 tokens per session scan A 889f291cd766
scrub is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 4,068 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.