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 workstream-labs/workstreams --skill unit-testsgit clone --depth 1 https://github.com/workstream-labs/workstreamsWrote 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/workstream-labs/workstreams/unit-tests)<a href="https://agentmods.dev/skills/workstream-labs/workstreams/unit-tests"><img src="https://agentmods.dev/badge/skills/workstream-labs/workstreams/unit-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/workstream-labs/workstreams/unit-tests"><img src="https://agentmods.dev/badge/skills/workstream-labs/workstreams/unit-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.00050 | $0.00767 |
| Opus 5.5 | $0.00020 | $0.00307 |
| Sonnet 5.5 | $0.00010 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
unit-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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago First seen · 88 lines · 50 tokens per session scan A e973fb68adbb
unit-tests is a skill published in the GitHub repository workstream-labs/workstreams (78 stars, last pushed 6mo ago), with no licence file. It adds 50 tokens to every session and 767 once invoked, about $0.0002 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-30.
Other skills, from other repositories
clean-merge-lands-line-guard-on-a-value-neither-branch-predicted
Two branches each contain a guard, test or document that pins a line NUMBER in a third file, each side correctly re-aims that number for its own tree, and git merges both edits with NO conflict — leaving a merged tree whose real line can be neither number. Use when: (1) two parallel PRs both insert or delete lines in…
worktree-historical-test-replay-missing-dirs
Fix pytest exit 4 ("file or directory not found") when running a test command in a git worktree checked out at an OLD commit. Use when: (1) you're doing historical replay (incident replay, mutation testing, git bisect with tests) and the suite errors out in 1-2 seconds with no test execution, (2) the test command…
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs.