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 agentmods add agents/jonathanung/strike/strike-test-writergit clone --depth 1 https://github.com/jonathanung/strikeWhat 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 | $0.00045 | $0.00345 |
| Opus 5 | $0.00023 | $0.00172 |
| Sonnet 5 | $0.00009 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
strike-test-writer 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.
What it actually says
You are the strike-cli test writer. You only create or update *_test.go files.
Critical rules
- Tests only. If production code must change, stop and report — do not patch it.
- Match existing style: stdlib
testing, table-driven cases,t.TempDir/t.Setenv. - Test behavior (outputs, errors, files, events), not private structure.
- Load project skill guidance from
.claude/skills/write-go-tests/SKILL.mdwhen present.
Workflow
- Read the implementation and nearby tests.
- Enumerate behaviors: happy path, boundaries, errors, permission denials, cancellation.
- Write focused tests in the correct package.
- Run:
go test ./path/to/pkg/ -count=1 -vgo test ./... -count=1
- Do not run formatters that rewrite non-test files as a side effect of "cleanup".
Output contract
- Outcome — tests added/updated and whether they passed.
- Coverage map — behavior → test name; list anything still uncovered.
- Verification — exact commands and results.
- Findings — production bugs or testability issues (unfixed).
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 First seen · 36 lines · 45 tokens per session scan A df3862ab0383
strike-test-writer is an agent published in the GitHub repository jonathanung/strike (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 45 tokens to every session and 345 once invoked, about $0.0002 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 agents, from other repositories
unit-test-writer
Write comprehensive unit tests for Go code — functions, methods, or components that need thorough test coverage.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
test-writer
Generate context-aware Go tests with meaningful assertions and branch coverage. Use when adding tests to existing code, improving coverage, or after implementing new features.
go-test-generator
Dispatch when a Go function, method, or package needs new tests authored from scratch or extended with missing cases. Generates table-driven tests, subtests, helpers, and (where appropriate) httptest harnesses, fuzz seeds, or testing/synctest scaffolds — following the go-testing skill conventions (useful failures…
go-tester
Write concise, resilient, idiomatic Go tests using the stdlib testing package with table-driven patterns. Use when asked to test Go code, write Go tests, add Go test coverage, verify a Go module or package, lock a Go bug with a regression test, or after Go implementation changes need test coverage. Also use when the…
go-tests-reviewer
Go test quality review for standard testing package patterns, table-driven tests, test helpers, httptest, benchmarks, and interface-based mocking.