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/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/sweep)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/sweep"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/sweep/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/rjwalters/kicad-tools/sweep"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/sweep.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.03571 |
| Opus 5.5 | $0.00000 | $0.01428 |
| Sonnet 5.5 | $0.00000 | $0.00714 |
| Haiku 4.5 | $0.00000 | $0.00357 |
Grade A, and why
sweep 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 2d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sweep
Process an explicit list of issues — or an explicit/NL-described set of open PRs — through the appropriate lifecycle from the current Claude session, no external daemon required. Runs sequentially by default, or in parallel waves of up to N builders when --builders-per-wave N is supplied (issue-set modes only). Supports --dry-run to preview the candidate plan without mutating anything.
Scope. This skill accepts either an explicit list of issue numbers, a natural-language description of which issues to process, or an explicit/NL-described list of open PRs (Mode C, the "back half" of the lifecycle: Judge → Doctor → Merge per PR's current label). Runs the appropriate lifecycle in waves. Supports
--dry-runto preview the plan without mutations. Other knobs sketched in #3298 are deliberately deferred — see "Limitations" below.If you need multi-account autonomous dispatch across many issues, use
/loom:loom(it drives theloom-daemon)./loom:sweepis itself the single-issue lifecycle, and also covers the in-between case: "I have these N issues (or PRs), run them in this session, without spinning up a daemon."
⚠️ --body @path Does NOT Expand — It Posts the Literal String
If you (or a role you dispatch) post a comment via gh issue comment / gh pr comment / gh api ... comments from a scratch file, --body @path (and gh api -f body=@path) posts the literal string @path, not the file's contents.
Full pitfall, incident citation, and fixes:
comment-body-literal-path.md.
How to use this skill (progressive disclosure)
This file is a dispatcher. It carries only what every /loom:sweep
invocation needs: the scope note above, the reference-file map below, the
hard Constraints, and the pointer list. Every procedure — argument parsing,
backend detection, the dry-run gate, both wave lifecycles, the summary
vocabulary — lives in a sibling sweep-*.md file in this same directory.
Read the files the run actually reaches, and only those.
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.
- 2d ago Changed 6ae19b0a7fdf
- 3d ago Changed · +1 lines 9e1844ede660
- 5d ago Changed · +1 lines e40f1f75576e
- 16d ago Changed · -5 lines 119a128d86f8
- 20d ago Changed a294118cdead
- 28d ago Changed 72e01bf32500
- 1mo ago First seen · 138 lines · 0 tokens per session scan A bfecca43d330
sweep is a command published in the GitHub repository rjwalters/kicad-tools (70 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,571 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-09-17.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.