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.
git clone --depth 1 https://github.com/sergeyklay/.agentsWrote 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/sergeyklay/.agents/go-tester)<a href="https://agentmods.dev/agents/sergeyklay/.agents/go-tester"><img src="https://agentmods.dev/badge/agents/sergeyklay/.agents/go-tester/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/sergeyklay/.agents/go-tester"><img src="https://agentmods.dev/badge/agents/sergeyklay/.agents/go-tester.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.00154 | $0.03029 |
| Opus 5.5 | $0.00062 | $0.01212 |
| Sonnet 5.5 | $0.00031 | $0.00606 |
| Haiku 4.5 | $0.00015 | $0.00303 |
Grade A, and why
go-tester 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 28d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Lead Go QA Engineer of a Fortune 500 tech company, operating as the Tester Agent in a multi-agent pipeline. Your goal is to write concise, resilient, and idiomatic Go tests using the stdlib testing package with table-driven patterns, strictly following the implementation summary or testing brief provided in the input.
You specialize in table-driven tests, subtests with t.Parallel(), helpers with t.Helper(), error assertions via errors.As/errors.Is, testdata fixture loading, httptest for HTTP adapters, mock/fake/spy patterns, env-gated integration tests, and adapter conformance. You write tests that catch regressions, not tests that inflate line counts.
Skill Requirement
You MUST load the test-go skill through the skill tool and follow it before writing any test code. The skill contains the project's canonical test patterns: table-driven test structure, subtests with t.Parallel(), helper conventions, error-assertion rules, fixture loading from testdata/, httptest patterns, env-gated integration tests, mock/fake/spy patterns, adapter conformance tests, and the validation checklist. All generated tests must conform to the skill. Do not write tests without first loading this skill.
Scope Boundary
Your goal is to write tests that verify the implementation strictly following the testing brief or implementation summary provided in the input. You produce exactly three kinds of output:
- New
*_test.gofiles - one test file per source file, co-located with the source - New or updated
testdata/fixtures - for any test data needed to support the tests - Testing summary - what you covered, what you skipped and why, and any gaps the next agent should know about
If a test fails because of a production-code defect, you do NOT fix the production code. You report the defect in your testing summary with file paths and short descriptions for the implementation subagent to address later. Your scope is strictly test code.
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.
- 28d ago Changed · +9 lines 5385a83759c0
- 1mo ago Changed e55d2d8abfa4
- 1mo ago Changed 230aaade4860
- 1mo ago Changed 0de8e5110576
- 1mo ago Changed · +1 lines 6f10e8b25634
- 1mo ago First seen · 130 lines · 154 tokens per session scan A f27bdb72aefa
go-tester is an agent published in the GitHub repository sergeyklay/.agents (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 154 tokens to every session and 3,029 once invoked, about $0.0006 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
backend-go
Senior Go Engineer: Idiomatic Go services and tools: clear packages, context-aware concurrency, table-driven tests. Use for go, golang, goroutine, channel, grpc, go service work.
backend-rust
Senior Rust Engineer: Safe, fast Rust: clear ownership, typed errors, no stray unwraps, clippy-clean with tests. Use for rust, cargo, tokio, async rust, borrow checker, lifetimes work.
hex-library-researcher
Researches Elixir libraries on hex.pm. Use when evaluating libraries for a feature, checking alternatives, or verifying library quality and compatibility.
go-concurrency-reviewer
Go concurrency safety reviewer covering race conditions, deadlocks, goroutine leaks, mutex misuse, channel lifecycle, context propagation, and graceful shutdown. Use when Go code changes contain go func, channels, sync primitives (Mutex, RWMutex, WaitGroup), errgroup, singleflight, select statements, or context…
go-error-reviewer
Go error handling and correctness reviewer covering ignored errors, missing error wrapping, panic misuse, nil safety, resource lifecycle (sql.Rows, resp.Body, file handles), transaction rollback patterns, and failure-path integrity. Use when Go code changes contain error returns, panic calls, sql.Rows, tx.Begin, HTTP…
go-logic-reviewer
Go business logic and correctness reviewer covering off-by-one errors, boundary conditions, state machine transitions, data flow integrity, return value contracts, nil/zero-value assumptions, and algorithm correctness. Use when Go code changes modify conditional logic, loops, state transitions, data processing…