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 instructions/hiromaily/docs-ssot/go-testgit clone --depth 1 https://github.com/hiromaily/docs-ssotWrote 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/instructions/hiromaily/docs-ssot/go-test)<a href="https://agentmods.dev/instructions/hiromaily/docs-ssot/go-test"><img src="https://agentmods.dev/badge/instructions/hiromaily/docs-ssot/go-test.svg" alt="Measured on agentmods" 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.01660 | $0.01660 |
| Opus 5 | $0.00830 | $0.00830 |
| Sonnet 5 | $0.00332 | $0.00332 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
docs-ssot go-test.instructions.md 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 5d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Test Rules
These rules apply to all *_test.go files in mcp-server/. Read them before writing any test.
Package declaration
Choose based on whether the test needs unexported symbols:
- Same package (
package orchestrator): when the test needs access to unexported types, functions, or variables. Used inorchestrator/and other pure-logic packages. - External package (
package state_test): when tests should only touch the exported API. Used instate/andtools/to keep tests honest about the public surface.
Do not mix both styles in the same directory.
Parallelism
Every test function and every t.Run subtest must call t.Parallel() as its first statement. This is enforced by the tparallel linter.
func TestFoo(t *testing.T) {
t.Parallel()
t.Run("case", func(t *testing.T) {
t.Parallel() // required inside every t.Run subtest
...
})
}
Exception: tests that mutate OS-level global state (environment variables, working directory) must NOT call t.Parallel(). Add a comment explaining why.
In Go 1.22+, the loop variable in for _, tc := range tests is scoped per iteration — tc := tc capture workarounds are not needed and must not be added.
Table-driven tests
Use table-driven tests with t.Run when two or more cases share the same function signature and assertion pattern. Do not write individual TestFoo_CaseA, TestFoo_CaseB functions for structurally identical cases — merge them into one table.
tests := []struct {
name string
input string
want string
}{
{name: "foo", input: "a", want: "b"},
{name: "bar", input: "c", want: "d"},
}
for _, tc := range tests {
t.Run(tc.name, func(t *testing.T) {
t.Parallel()
got := fn(tc.input)
if got != tc.want {
t.Errorf("fn(%q) = %q, want %q", tc.input, got, tc.want)
}
})
}
For 2D matrix tests (e.g. sourceType × effort), use tc.sourceType+"/"+tc.effort as the subtest name — the / creates a hierarchy that makes -run filtering precise.
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.
- 5d ago First seen · 193 lines · 1,660 tokens per session scan A c87672d2205e
docs-ssot go-test.instructions.md is an instructions file published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,660 tokens to every session, about $0.0083 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 instructions, from other repositories
azure-sdk-for-go go-tests.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
go-enumsafety GEMINI.md
Gemini CLI instructions for Djarvur/go-enumsafety, covering go-enumsafety development guidelines, active technologies, project structure, commands and run tests with coverage.
ksail go-testing.instructions.md
Use when writing or editing Go test files, creating unit tests, benchmarks, or test helpers. Covers KSail's testing conventions, table-driven patterns, and the exporttest.go seam.
instrMCP CLAUDE.md
Claude Code instructions for caidish/instrMCP, covering claude.md, development commands, always use conda environment instrmcpdev for testing, unit tests (fast, no hardware required - all mocked) and e2e tests (requires playwright and browser automation).
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).
ksail go-code.instructions.md
Use when writing or editing Go source files in the KSail codebase. Covers error handling, path safety, dependency guard, and package organization conventions.