Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install disciplineWrote 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/melodic-software/claude-code-plugins/sweep-all)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/sweep-all"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/sweep-all/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/melodic-software/claude-code-plugins/sweep-all"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/sweep-all.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.00107 | $0.02876 |
| Opus 5.5 | $0.00043 | $0.01150 |
| Sonnet 5.5 | $0.00021 | $0.00575 |
| Haiku 4.5 | $0.00011 | $0.00288 |
Grade A, and why
sweep-all 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 5d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sweep all disciplines
A declared second species in this plugin: NOT a corrector. It carries no
discipline of its own; it is a pure router that COMPOSES the correctors into a
single batched re-anchor pass. The disciplines live in the correctors, the
shared method lives in
${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md,
and membership + order live in each corrector's own tier metadata. This skill
names no members: it globs and reads them.
Two modes
- Session-start digest (cheap, default when nothing has happened yet). Derive the posture from the skill listing and each corrector's tier metadata. NO corrector bodies load, NO audit runs. Report which correctors are core (run every session), which are situational (relevance-gated), and which are never-batched. This is the conversation-start case: set posture, audit nothing.
- Full batch pass (mid-session, or on explicit request). Preflight that the fan-out can inherit this conversation (mandatory. See Preflight), then fan out an audit-only subagent per in-scope corrector and apply their corrections once, on the main thread, in a fixed order (below). A failed preflight degrades to mode 1 with the exact degrade token as the report's first line (see Preflight).
Resolving membership (never named inline)
Glob the sibling corrector directories and read each one's
metadata.discipline-batch (core / situational / never) and
metadata.discipline-batch-rank.
- core. In scope every session.
- situational. In scope only when relevant to THIS conversation. Route from the corrector's own listing description (its trigger phrases and "at conversation start on …" clause), not from a guess. Report which situational correctors were included and which were skipped and why. A skip is always reported, never silent.
- never. Excluded from the batch by execution or interaction class
(correctors that need a non-fork fresh context or stop to remediate with
the user). Membership is whichever correctors declare
discipline-batch: never. Report that they exist (from the glob) and are invoked directly, not batched.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · -6 lines 991d6bc2d199
- 7d ago Changed · +28 lines 19fe59c89513
- 8d ago Changed · +8 lines e948885b6880
- 22d ago Changed · -37 tokens per session 21ad0c4680ad
- 1mo ago Changed · +3 lines fb0163e32bf8
- 1mo ago Changed · -13 lines · -26 tokens per session cccb1321b150
- 1mo ago First seen · 187 lines · 170 tokens per session scan A 6aa9261d3a67
sweep-all is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 107 tokens to every session and 2,876 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
validate-before-process
For input validation: check format and constraints before processing, fail fast with clear errors, defensive parsing.