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/skills/write-go-tests/SKILL.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/skills/jonathanung/strike/write-go-tests)<a href="https://agentmods.dev/skills/jonathanung/strike/write-go-tests"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/write-go-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/jonathanung/strike/write-go-tests"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/write-go-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.00054 | $0.00984 |
| Opus 5.5 | $0.00022 | $0.00394 |
| Sonnet 5.5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
write-go-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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Go tests (strike-cli)
Tests only. Never modify production code; if code is untestable or buggy, report it.
Conventions
- Framework: stdlib
testingonly. - Placement:
package footests beside source asfoo_test.go(same package is fine and preferred for unexported helpers). - Style: table-driven where multiple inputs matter; plain functions for stateful sequences.
- Isolation:
t.TempDir(),t.Setenv, never touch real~/.strikeor network withouthttptest. - Assert observable behavior (return values, files written, events emitted, errors), not private call graphs.
- Bug fixes: add at least one regression test that fails before the fix when feasible.
Helpers by domain
Tools (harness/tool)
func allowAll(dir string) *Context {
return &Context{
WorkDir: dir, // usually t.TempDir()
Ask: func(ctx context.Context, req AskRequest) error { return nil },
}
}
Cover where relevant: happy path, invalid JSON args, permission rejection via Ask error,
path relative/absolute, workspace sandbox escape attempts, filestate stale read after
external change, truncation/output caps, deferred/toolsearch registration.
Tool surface is large (read/glob/grep/edit/write/apply_patch/bash + sandbox, task*, webfetch, todo*, memory_, issue_, notebook_edit, sleep, skill, question, plan_mode, phase_done, toolsearch, …). Prefer tests next to the module you touch; do not assume a fixed “six tools” list.
Permissions (harness/permission)
Evaluatelast-match-wins across layered rulesets.Service.Ask+Reply: once, always (session grant + sibling resolve), reject cascade, ctx cancel.
Protocol / session
- Round-trip event types through
protocol.Wrap→Envelope.Decodewhen adding kinds. - Session:
Open→Append→Close→Replay; malformed line errors.
Providers
- Prefer
httptest.NewServeragainstharness/providers/baseand concrete adapters. - Engine integration:
harness/provider/echo(prompts starting withrunemit bash tool calls).
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 · 95 lines · 54 tokens per session scan A 33ea3accf20c
write-go-tests is a skill published in the GitHub repository jonathanung/strike (5 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 984 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 skills, from other repositories
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
timeouts-and-async
Make Ginkgo specs interruptible and test asynchronous behavior — SpecContext/context.Context cancellable nodes, NodeTimeout/SpecTimeout/GracePeriod, the --timeout flag, Abort and SIGINT behavior, Gomega Eventually/Consistently (the func(g Gomega) form, .WithContext), and the defer GinkgoRecover() rule for goroutines.…
setup
Wire Ginkgo into a Go package — install the ginkgo CLI and Ginkgo+Gomega, ginkgo bootstrap to generate the suitetest.go (TestXxx/RegisterFailHandler(Fail)/RunSpecs), the package xxxtest convention, dot-import alternatives (aliased import, dsl/ subpackages, --nodot), ginkgo generate, and testing.T interop via…
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…
eng-test-conventions
Go test-shape discipline for Compozy. Use when writing or editing test.go under cmd or internal after test placement is justified. Do not use for non-Go tests, fixture-only changes, or as a replacement for eng-consolidate-test-suites.