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 nirecom/agents --skill sweep-testsgit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/sweep-tests)<a href="https://agentmods.dev/skills/nirecom/agents/sweep-tests"><img src="https://agentmods.dev/badge/skills/nirecom/agents/sweep-tests/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/nirecom/agents/sweep-tests"><img src="https://agentmods.dev/badge/skills/nirecom/agents/sweep-tests.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.00023 | $0.01039 |
| Opus 5.5 | $0.00009 | $0.00416 |
| Sonnet 5.5 | $0.00005 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
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 9d 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 — 44 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_MAIN_ROOT/bin/audit-tests.sh" [--dry-run] [--apply] [--stale-months N] [--offline] [--format text|json] [--fix-headers] — issue-specific scope.
STE-2. Run bash "$AGENTS_MAIN_ROOT/bin/audit-tests-common.sh" [--dry-run] [--apply] [--stale-months N] [--offline] [--format text|json] [--fix-headers] — scope:common.
STE-3. Run bash "$AGENTS_MAIN_ROOT/bin/audit-tests.sh" --dup-groups — corpus-wide # Tests: duplicate-group inventory. Pass no other flag.
Case-marker embedding (on request only)
STE-4. Only when case-marker embedding is requested: run bash "$AGENTS_MAIN_ROOT/bin/audit-tests.sh" --embed-cases [--band-size N] [--order frequency|priority] [--dry-run], dispatch one subagent per ITEM row of the <<<EMBED-GATE-STE4 block, then run bash "$AGENTS_MAIN_ROOT/bin/audit-tests.sh" --embed-apply <EMBED_WORKDIR>.
Each embed prompt carries the canonical line of the rules/shell-commands.md Subagent Dispatch Prompts section.
Rules
- Every STE-1..STE-4 output is printed verbatim; never summarize or filter one.
--embed-casescovers the whole corpus and behaves the same from either entrypoint, so call one.- An embed subagent reads its
rules_doc(andfailure.txton a retry) and writes only itsoutputdirectory andreport.txt. - On a
<<<EMBED-RETRY-STE4block, dispatch once more for those rows only, then rerun--embed-applyon the same workdir; no second retry block follows. - Copy
CAPPED,TOOL_FAILED,CODEX_UNAVAILABLE,MERGED_TARGETandEXEMPTlines into the PR body's verification report; aTOOL_FAILEDfile is picked again by the next run. - The embed protocol (worklist, gate rows, states, retry record) is owned by
docs/architecture/claude-code/sweep-tests-embed-cases.md. - For marker-bearing files (
case_begin/case_end), candidacy is per case: a case qualifies when its target is gone (partial-orphan); all cases gone → whole-file orphan. For files without markers, 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 ships with it
1 file 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.
- 9d ago Changed · +1 lines d6cad54d8287
- 11d ago Changed ea6ca6eb6ef1
- 14d ago Changed · +9 lines 7793dfee7bbb
- 28d ago Changed f4523e5bfb06
- 1mo 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 today), licensed MIT. It adds 23 tokens to every session and 1,039 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.