Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-pynpx agentmods add commands/terrene-foundation/kailash-coc-claude-py/sweepWrote 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/terrene-foundation/kailash-coc-claude-py/sweep)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/sweep"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/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/terrene-foundation/kailash-coc-claude-py/sweep"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/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.00040 | $0.06095 |
| Opus 5 | $0.00020 | $0.03047 |
| Sonnet 5 | $0.00008 | $0.01219 |
| Haiku 4.5 | $0.00004 | $0.00609 |
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 8d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
A /sweep is the structural defense against "I think we're done." Before declaring a session converged or starting fresh work, surface every class of outstanding item: in-flight todos, open GH issues (this repo), spec-vs-code redteam gaps, stale workspace state, and process-hygiene gaps.
Distinct from /redteam (scopes to ONE workspace's spec compliance) — /sweep is repo-wide and rolls every workspace's redteam status into one view.
Project-scoped by default — Sweeps 1-8 target the CURRENT repo only. They do NOT compare against sibling SDK repos, PyPI, or BUILD-only state. BUILD repos (kailash-py, kailash-rs) maintain a richer LOCAL commands/sweep.md with cross-SDK + sibling-package + source-protection sweeps; do not edit those from here. Orchestration-root exception: Sweep 9 (below) adds a cross-ecosystem roll-up that fires only where an operator has DECLARED an ecosystem resolver config and the clone is not a declared consumer role — canonically loom (rules/repo-scope-discipline.md § Exceptions). It self-detects and emits an N/A sentinel otherwise, so the distributed command stays byte-identical on the 30+ downstream consumers (which carry no resolver config).
Execution Model
Autonomous — runs every sweep sequentially, accumulates findings into a single management decision report (.claude/skills/sweep/ § 1). Every finding is CATEGORY-classified per rules/product-completion-first.md (BUG / INVEST-NOW ISSUE / INCREMENTAL IMPROVEMENT — severity ranks, never gates fix-vs-defer): BUG + INVEST-NOW → FIX-NOW (invest-now judgment calls surfaced at the report's Decision Points for co-owner direction); INCREMENTAL → the deferred-quality tracking list under the four generalized zero-tolerance.md Rule-1b conditions. The agent MAY fix trivial BUGs inline (per rules/zero-tolerance.md Rule 1: "if you found it, you own it") but MUST surface every finding with its category + disposition; a completion-blocking finding deferred as "incremental" is BLOCKED (product-completion-first.md MUST-2).
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.
- 8d ago First seen · 176 lines · 40 tokens per session scan A 69da8f635942
sweep is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 24d ago), licensed Apache-2.0. It adds 40 tokens to every session and 6,095 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.