Borrowing it
Nothing to install: this file belongs to dip497/hivemind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dip497/hivemind/main/.claude/skills/test-audit/SKILL.mdgit clone --depth 1 https://github.com/dip497/hivemindWrote 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/dip497/hivemind/test-audit)<a href="https://agentmods.dev/skills/dip497/hivemind/test-audit"><img src="https://agentmods.dev/badge/skills/dip497/hivemind/test-audit/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/dip497/hivemind/test-audit"><img src="https://agentmods.dev/badge/skills/dip497/hivemind/test-audit.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.00071 | $0.01109 |
| Opus 5.5 | $0.00028 | $0.00444 |
| Sonnet 5.5 | $0.00014 | $0.00222 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
test-audit 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test audit
The maintainer's rule: every test written or changed here passes this gate. It is adapted
from openclaw's test-audit skill
(MIT, © 2026 OpenClaw Foundation): the gate, the junk patterns and the retention bar are
theirs, and the commands and examples are ours.
Authoring gate
Before adding or changing a test, answer four questions. A missing answer means the test does not go in yet.
- What observable behaviour, invariant or independent contract does it protect?
- What credible regression makes it fail?
- Why does existing coverage not already catch that? Each contract has one owner test at the strongest boundary. Another layer needs its own distinct risk, such as a transport, lifecycle or wiring failure the owner cannot reach. Prefer a new row in a table-driven test, or a shared fixture, over a near-duplicate test.
- Does it need a production seam (an export, option, flag, clock, hook) that no production caller needs? Then test at the real boundary and do not add the seam.
A test that would break under a behaviour-preserving refactor is asserting implementation. Rewrite it at the owning boundary before it lands.
Junk patterns
A match fails the gate unless the retention bar below names the contract it guards.
- assertion-free coverage probes; self-comparisons;
- copied fixtures, inventories, manifests or export lists;
- exact source, import or string greps;
- call-shape tests (call counts, "called with") of private helpers that real boundaries cover;
- the same contract asserted again in another test or at another layer;
- tests that exist to keep a test-only export, global or wrapper alive, and production code whose only callers are tests;
- expected values produced by the code under test (building the expected storage key with the key builder that the code also uses);
- mocks that implement the asserted behaviour; one mock standing in for different APIs;
- fixtures that supply what the code should produce; persistence asserted against a store the code never writes;
- negative controls that pass for an unrelated reason ("a corrupt blob starts fresh" planted under a key the code never reads passes whatever the code does);
- names that promise more than the test exercises.
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 Changed · +6 lines 21d685ba5707
- 12d ago First seen · 79 lines · 71 tokens per session scan A 551a3d2bb207
test-audit is a skill published in the GitHub repository dip497/hivemind (17 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,109 once invoked, about $0.0003 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-10-18.
Other skills, from other repositories
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
test-review
You are an expert DataHub test reviewer. Your role is to evaluate pytest smoke tests against established testing standards, identify issues, and provide actionable feedback.
grade-tests
Grade curated individual tests for readiness, A-F quality and improvements. ALWAYS USE FOR: grade tests, review only a named test, per-test readiness or quality bands for supplied methods, bodies, file spans or bounded PR diffs, including existing tests. Return Pass/Failed/Uncertain/Not applicable; unresolved/empty…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.