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.
npx skills add simota/agent-skills --skill sweepgit clone --depth 1 https://github.com/simota/agent-skillsWrote 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/simota/agent-skills/sweep)<a href="https://agentmods.dev/skills/simota/agent-skills/sweep"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/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/skills/simota/agent-skills/sweep"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/sweep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 6 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Excessive Agency · line 83 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 92 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.05299 |
| Opus 5 | $0.00020 | $0.02649 |
| Sonnet 5 | $0.00008 | $0.01060 |
| Haiku 4.5 | $0.00004 | $0.00530 |
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 6d 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sweep
Sweep identifies cleanup candidates and proposes safe deletions. Prefer evidence over intuition, reversibility over speed, and preservation over aggressive pruning.
What ships with it
21 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.
- _common 10 B
- reference/autorun-schema.md 613 B
- reference/cleanup-anti-patterns.md 2.6 KB
- reference/cleanup-protocol.md 4.5 KB
- reference/cleanup-targets.md 2.3 KB
- reference/dead-code-impact-prevention.md 1.8 KB
- reference/dependency-cleanup.md 2.9 KB
- reference/detection-strategies.md 3.6 KB
- reference/exclusion-patterns.md 1.0 KB
- reference/false-positives.md 3.2 KB
- reference/imports-cleanup.md 7.1 KB
- reference/kotlin-cheatsheet.md 6.8 KB
- reference/language-patterns.md 7.2 KB
- reference/large-scale-cleanup.md 1.6 KB
- reference/maintenance-workflow.md 3.6 KB
- reference/rust-cheatsheet.md 5.0 KB
- reference/sample-commands.md 1.2 KB
- reference/stale-comments.md 6.0 KB
- reference/swift-cheatsheet.md 5.4 KB
- reference/troubleshooting.md 2.1 KB
- reference/unused-types.md 7.3 KB
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.
- 6d ago First seen · 279 lines · 40 tokens per session scan A 960a5da0e195
sweep is a skill published in the GitHub repository simota/agent-skills (76 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 5,299 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 skills, from other repositories
langsmith-tracing
LangSmith tracing and debugging setup for LLM applications. Configure observability, capture traces, and enable debugging for LangChain/LangGraph agents.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
systematic-debugging
Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and resolve defects.
debugging-patterns
Root cause analysis frameworks including log-first investigation, git bisect correlation, and pattern-based diagnosis with confidence scoring.
hotfix-triage
Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes.