Borrowing it
Nothing to install: this file belongs to schmitthub/clawker. 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/schmitthub/clawker/main/.agents/skills/test-hunter/SKILL.mdgit clone --depth 1 https://github.com/schmitthub/clawkerWrote 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/schmitthub/clawker/test-hunter)<a href="https://agentmods.dev/skills/schmitthub/clawker/test-hunter"><img src="https://agentmods.dev/badge/skills/schmitthub/clawker/test-hunter/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/schmitthub/clawker/test-hunter"><img src="https://agentmods.dev/badge/skills/schmitthub/clawker/test-hunter.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.00045 | $0.05688 |
| Opus 5.5 | $0.00018 | $0.02275 |
| Sonnet 5.5 | $0.00009 | $0.01138 |
| Haiku 4.5 | $0.00005 | $0.00569 |
Grade A, and why
test-hunter scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Each test verifies observable system behavior (curl succeeds/fails through How it starts
The opening of the file, as written. The whole thing — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an adversarial test quality auditor. Your job is not to check coverage — it's to find tests that shouldn't exist. Every test you review must justify its existence by answering one question: "What production bug would go undetected if this test were deleted?" If the answer is "none," the test is waste.
Why this matters
AI agents generate high volumes of tests that look productive but often test nothing meaningful. These tests:
- Create false confidence ("we have 94% coverage!")
- Slow down CI pipelines
- Add maintenance burden when production code changes
- Obscure the tests that actually matter
- Make developers numb to test failures
The goal is a lean, meaningful test suite where every test earns its keep.
Scope
Audit only tests that are new or modified in the current change. Use git diff to determine scope:
# For PR reviews
git diff main...HEAD --name-only | grep -E '(test_|_test\.|\.test\.|\.spec\.|tests/)'
# For completion gates (unstaged work)
git diff --name-only | grep -E '(test_|_test\.|\.test\.|\.spec\.|tests/)'
If neither produces results, audit the test files you were pointed to.
Clawker project context
This is a Go CLI project. Key testing details:
- Test framework: Standard
testingpackage +testify/assert+testify/require - Test file convention:
*_test.goin the same package (white-box) or_testsuffix package (black-box) - Test naming:
TestFunctionName_Scenarioor table-driven witht.Run(name, ...) - Mocks:
moq-generated mocks in<package>/mocks/subpackages — never hand-edited - Fakes: Hand-written fakes in
<package>test/or<package>/mocks/subpackages (e.g.,mocks.FakeClient,gittest.InMemoryGitManager) - Test environment:
testenv.New(t)for isolated XDG dirs + config + project manager - Golden files:
GOLDEN_UPDATE=1env var to regenerate; tests compare againsttestdata/files - Integration tests: Live in
test/directory tree (Docker required), separated from unit tests - Unit tests:
make testruns all unit tests (excludestest/cli,test/internals,test/agents)
What ships with it
2 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.
- 1mo ago First seen · 531 lines · 45 tokens per session scan A 124d57827c9c
test-hunter is a skill published in the GitHub repository schmitthub/clawker (58 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 5,688 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other skills, from other repositories
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.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
code-review
Review a diff against its acceptance criteria in four segments (convention adherence, bug scan, historical-context regressions, test-coverage gaps) as a NON-implementing agent. Findings are sorted by severity, each with file:line + a failure scenario. A planted defect must be caught; a clean diff must not be…
testing-patterns
Testing patterns for Spring Boot - JUnit 5, Mockito, MockMvc, Testcontainers, positive and negative test cases. Use when user asks about testing, writing tests, test coverage, or test failures.