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 skills add daibang123a/golang-agent-skills --skill go-testing-guidelinesgit clone --depth 1 https://github.com/daibang123a/golang-agent-skillsWrote 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/daibang123a/golang-agent-skills/go-testing-guidelines)<a href="https://agentmods.dev/skills/daibang123a/golang-agent-skills/go-testing-guidelines"><img src="https://agentmods.dev/badge/skills/daibang123a/golang-agent-skills/go-testing-guidelines/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/daibang123a/golang-agent-skills/go-testing-guidelines"><img src="https://agentmods.dev/badge/skills/daibang123a/golang-agent-skills/go-testing-guidelines.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.00086 | $0.02637 |
| Opus 5 | $0.00043 | $0.01319 |
| Sonnet 5 | $0.00017 | $0.00527 |
| Haiku 4.5 | $0.00009 | $0.00264 |
Grade A, and why
go-testing-guidelines 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 11d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Testing Guidelines
Comprehensive testing best practices for Go. 30+ rules covering unit tests, integration tests, benchmarks, fuzzing, and test organization.
How It Works
- Agent identifies the testing need (unit, integration, benchmark, fuzz)
- Agent applies the appropriate patterns from this skill
- Agent generates test code following Go conventions
- Agent ensures proper cleanup, parallelism, and naming
Rules
1. Table-Driven Tests (Critical)
| # | Rule | Description |
|---|---|---|
| TD1 | Use table-driven tests for multiple cases | Define test cases as a slice of structs. Each case has a name and inputs/expected outputs. |
| TD2 | Name test cases descriptively | "empty input", "negative number", "unicode string" — names appear in test output. |
| TD3 | Use t.Run for subtests | Enables running individual cases: go test -run TestFoo/empty_input. |
| TD4 | Run subtests in parallel when safe | Call t.Parallel() in subtests for independent test cases. Capture loop variable. |
| TD5 | Include error cases | Always test error paths, edge cases, and boundary conditions. |
func TestParseAge(t *testing.T) {
tests := []struct {
name string
input string
want int
wantErr bool
}{
{name: "valid age", input: "25", want: 25},
{name: "zero", input: "0", want: 0},
{name: "negative", input: "-1", wantErr: true},
{name: "not a number", input: "abc", wantErr: true},
{name: "empty string", input: "", wantErr: true},
{name: "overflow", input: "999999", wantErr: true},
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
t.Parallel()
got, err := ParseAge(tt.input)
if tt.wantErr {
if err == nil {
t.Errorf("ParseAge(%q) expected error, got %d", tt.input, got)
}
return
}
if err != nil {
t.Fatalf("ParseAge(%q) unexpected error: %v", tt.input, err)
}
if got != tt.want {
t.Errorf("ParseAge(%q) = %d, want %d", tt.input, got, tt.want)
}
})
}
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 309 lines · 86 tokens per session scan A fb3ca049689a
go-testing-guidelines is a skill published in the GitHub repository daibang123a/golang-agent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 86 tokens to every session and 2,637 once invoked, about $0.0004 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 skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.