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 agentmods add skills/nirecom/agents/sweep-testsnpx skills add nirecom/agents --skill sweep-testsgit clone --depth 1 https://github.com/nirecom/agentsWhat 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 | $0.00023 | $0.00680 |
| Opus 5 | $0.00012 | $0.00340 |
| Sonnet 5 | $0.00005 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
sweep-tests 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retires test files whose # Tests: targets are gone. A flagless run deletes; --dry-run reports only.
Procedure
STE-1. Run bash "$AGENTS_CONFIG_DIR/bin/audit-tests.sh" [--dry-run] [--apply] [--stale-months N] [--offline] [--format text|json] [--fix-headers] — issue-specific scope.
STE-2. Run bash "$AGENTS_CONFIG_DIR/bin/audit-tests-common.sh" [--dry-run] [--apply] [--stale-months N] [--offline] [--format text|json] [--fix-headers] — scope:common.
STE-3. Run bash "$AGENTS_CONFIG_DIR/bin/audit-tests.sh" --dup-groups — corpus-wide # Tests: duplicate-group inventory. Pass no other flag.
Rules
- Every STE-1..STE-3 output is printed verbatim; never summarize or filter one.
- Candidacy is decided by target survival alone: a file qualifies once every
# Tests:path is gone. - Issue state never selects a candidate — it gates deletion only.
- Held deletions are reported as
SKIP_DELETE_ISSUE_ACTIVE,SKIP_DELETE_METADATA_UNAVAILABLE, orSKIP_DELETE_AMBIGUOUS_REF; the file stays listed and on disk. - 0
CANDIDATE:/ORPHAN:lines whileMALFORMED_HEADER:/NO_TESTS_HEADER:lines are present means the survival axis is clear and repair still remains on the header axis. - A dispatcher and its sibling
tests/<stem>/folder are retired as one unit. --dry-runsuppresses every write: no deletion, no header rewrite.--applyis an explicit synonym of the flagless default; both scripts accept it.--fix-headersreports format-invalid tokens (FIX_A:/FIX_B:) without rewriting; add--applyto rewrite# Tests:headers in-place (atomic, exec-bit preserved). Multi-paren tokens are excluded from auto-rewrite (SKIP_APPLY_MULTI_PAREN).--fix-headers --dry-runis report-only as well; no file is ever touched.--offlineskips GitHub API calls; candidates are still reported and deletion of issue-referencing files is held.--stale-months N(default 3) moves the delete-time staleness boundary only.--dup-groupsis read-only; combining it with explicit--apply,--fix-headers, or--format jsonexits 2.--dup-groupscovers the whole corpus and emits the same TSV from either entrypoint, so call one.- Missing, duplicated, late, and format-invalid headers become
skiprows by reason; they never join a group. keyandfilesare escaped; the decoding rule is in thebin/lib/test-dup-group.shheader.
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 First seen · 34 lines · 23 tokens per session scan A 8b389e597a96
sweep-tests is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 680 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.