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 khasky/awesome-agent-skills --skill awesome-regression-sweepgit clone --depth 1 https://github.com/khasky/awesome-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/khasky/awesome-agent-skills/awesome-regression-sweep)<a href="https://agentmods.dev/skills/khasky/awesome-agent-skills/awesome-regression-sweep"><img src="https://agentmods.dev/badge/skills/khasky/awesome-agent-skills/awesome-regression-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/khasky/awesome-agent-skills/awesome-regression-sweep"><img src="https://agentmods.dev/badge/skills/khasky/awesome-agent-skills/awesome-regression-sweep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00153 | $0.03593 |
| Opus 5 | $0.00077 | $0.01796 |
| Sonnet 5 | $0.00031 | $0.00719 |
| Haiku 4.5 | $0.00015 | $0.00359 |
Grade A, and why
awesome-regression-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 today.
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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regression Sweep
One question — did anything break — answered in layers, because the layers fail differently. A green unit suite says nothing about a byte format two independent implementations have to agree on; a passing suite says nothing about whether the code that is deployed is the code you tested; and a green working tree says nothing about the scheduled job that stopped running last night.
Everything here is read-only. No deploy, no database write, no mutating admin call, no destructive suite against production. When a check would need one, say so and stop rather than doing it.
Reference files (load the one the run needs):
references/live-contract-checks.md— the black-box checklist for a public read surface, the invariants of append-only and derived data, and the golden-vector method for cross-implementation parity.references/deployment-and-infrastructure.md— proving the deployed code is the tested code, and the infrastructure layer that fails with no code change at all.
Scripts (Node ≥18, no dependencies):
-
scripts/sweep.mjs— runs the aspect list from a config: one line per aspect, deltas against a stored baseline, per-aspect timeouts, output assertions for tools whose exit code lies, and aSKIPwhere a prerequisite is absent. -
scripts/http-contract.mjs— black-box probe of a public read endpoint: cache-key canonicalization, validation before work, CORS, ETag/304,HEADparity, security headers. -
Other runtimes — the runner is Node so one file works on every platform; the aspects it runs are the project's own commands, whatever the stack (
cargo test,go vet,pytest,mvn verify,dotnet build). If the project has no Node toolchain, run the aspect table by hand and keep the baseline in a text file — the runner is convenience, the table is the contract.
Scope and prerequisites
What ships with it
4 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.
- today Changed 5053b380b91e
- 5d ago Changed · +9 lines · -69 tokens per session 3c0a7980e244
- 11d ago First seen · 257 lines · 222 tokens per session scan A 0ad916c75a12
awesome-regression-sweep is a skill published in the GitHub repository khasky/awesome-agent-skills (8 stars, last pushed today), licensed MIT. It adds 153 tokens to every session and 3,593 once invoked, about $0.0008 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
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
verification-before-completion
A checklist for verifying work before claiming that it is finished, fixed, built, tested, or ready to submit. It requires fresh command output and evidence for each claim.
writing-skills
A guide for creating and testing reusable instructions for AI agents, called skills. It applies test-driven development, or TDD—the practice of writing tests before implementation—to instruction documents.
test-driven-development
Test-driven development, or TDD, is a way to build software by writing a test that fails, adding the smallest code that makes it pass, and then cleaning up the code. These instructions require that process for features, bug fixes, refactors, and behavior changes.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…