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/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/rules/hiromaily/docs-ssot/go-test)<a href="https://agentmods.dev/rules/hiromaily/docs-ssot/go-test"><img src="https://agentmods.dev/badge/rules/hiromaily/docs-ssot/go-test/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/rules/hiromaily/docs-ssot/go-test"><img src="https://agentmods.dev/badge/rules/hiromaily/docs-ssot/go-test.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.00000 | $0.01677 |
| Opus 5.5 | $0.00000 | $0.00671 |
| Sonnet 5.5 | $0.00000 | $0.00335 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
go-test 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 1mo 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 — 195 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.
- 1mo ago First seen · 195 lines · 0 tokens per session scan A 3b166ace3fd3
go-test is a cursor rule published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,677 tokens. 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 cursor rules, from other repositories
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
go
Idiomatic Go rules. Explicit error handling, interface-based design, context-first concurrency.
schema_test_implementation_guide
A concise and practical guide for building GoZod Schema test files, updated with the latest practices from stringtest.go, objecttest.go, and complextest.go.
go
Go development guidelines — error handling, concurrency, interfaces, context propagation, and testing. Applied when working with Go code.
mockery
Mockery Mock Generation Rules.
d-test-unit-test
A set of rules for writing unit tests in Go, the programming language used by the examples. It covers test names, table-driven cases, subtests, mocks, assertions, file placement, and basic test quality principles.