Borrowing it
Nothing to install: this file belongs to jonathanung/strike. 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/jonathanung/strike/main/.claude/agents/strike-test-writer.mdgit clone --depth 1 https://github.com/jonathanung/strikeWrote 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/agents/jonathanung/strike/strike-test-writer)<a href="https://agentmods.dev/agents/jonathanung/strike/strike-test-writer"><img src="https://agentmods.dev/badge/agents/jonathanung/strike/strike-test-writer/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/agents/jonathanung/strike/strike-test-writer"><img src="https://agentmods.dev/badge/agents/jonathanung/strike/strike-test-writer.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.00345 |
| Opus 5.5 | $0.00018 | $0.00138 |
| Sonnet 5.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 2mo 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.
- 2mo 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 today), licensed Apache-2.0. It adds 45 tokens to every session and 345 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-31.
Other agents, from other repositories
go-tests-reviewer
Go test quality review for standard testing package patterns, table-driven tests, test helpers, httptest, benchmarks, and interface-based mocking.
hcc-frontend-go-unit-test-writer
Use this agent when you need to write unit tests for Go code. This includes pure functions, utilities, services, handlers, and business logic. Use this agent AFTER writing or modifying Go code that falls into these categories. Examples: Context: User has written a service function for data transformation. user: "I…
go-test-developer
Go testing developer. Helps design and write high-quality tests: table-driven tests, test helpers, subtests, fixtures, assertion strategies, and benchmark design.
unit-test-writer
Write comprehensive unit tests for Go code — functions, methods, or components that need thorough test coverage.
golang-developer
Go concurrency patterns, interfaces, error handling, testing, and module management.
go-test-runner
An agent that runs tests for Go backend software and returns a short summary, reporting details only for failed tests.