go-test

go-test is a command for Claude Code, OpenCode from loulanyue/awesome-claude-notes. It costs 8 tokens per session (638 once invoked), scanned A, a copy of go-test, MIT.

A Go development workflow based on test-driven development, where tests are written before the code, using grouped test cases in one test function.

In plain words
What is it for?
Use it to design Go types and interfaces, write table-driven tests, implement the smallest passing solution, and check performance with benchmarks.
Why use it?
It helps define expected behavior first and catches incorrect results or errors while implementing the change.

Command for Claude CodeOpenCode

Written for Claude Code and OpenCode: $ARGUMENTS substitution, but also installed under .opencode/. Also seen: agent in frontmatter.

Part of the awesome-claude-notes plugin — 106 skills, 61 commands, 28 agents shipped together

Good fit Use it to design Go types and interfaces, write table-driven tests, implement the smallest passing solution, and check performance with benchmarks.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/loulanyue/awesome-claude-notes/go-test
Install

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.

Clone the repo
git clone --depth 1 https://github.com/loulanyue/awesome-claude-notes

Made for: Claude Code, OpenCode.

Or install awesome-claude-notes, the plugin that ships this one along with the rest of its 106 skills, 61 commands, 28 agents.

Wrote 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.

agentmods badge for go-test

README.md
[![agentmods](https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/go-test/github.svg)](https://agentmods.dev/commands/loulanyue/awesome-claude-notes/go-test)
Your own site
<a href="https://agentmods.dev/commands/loulanyue/awesome-claude-notes/go-test"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/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.

agentmods 80×15 button for go-test

Your own site · 80×15
<a href="https://agentmods.dev/commands/loulanyue/awesome-claude-notes/go-test"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/go-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 638 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.00638
Opus 5 $0.00004 $0.00319
Sonnet 5 $0.00002 $0.00128
Haiku 4.5 $0.00001 $0.00064

Measured 9d ago against content hash ff270caf17e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 9d 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.

Origin

This is a copy

100% identical to go-test — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.opencode/commands/go-test.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Go Test Command

Implement using Go TDD methodology: $ARGUMENTS

Your Task

Apply test-driven development with Go idioms:

  1. Define types - Interfaces and structs
  2. Write table-driven tests - Comprehensive coverage
  3. Implement minimal code - Pass the tests
  4. Benchmark - Verify performance

TDD Cycle for Go

Step 1: Define Interface

type Calculator interface {
    Calculate(input Input) (Output, error)
}

type Input struct {
    // fields
}

type Output struct {
    // fields
}

Step 2: Table-Driven Tests

func TestCalculate(t *testing.T) {
    tests := []struct {
        name    string
        input   Input
        want    Output
        wantErr bool
    }{
        {
            name:  "valid input",
            input: Input{...},
            want:  Output{...},
        },
        {
            name:    "invalid input",
            input:   Input{...},
            wantErr: true,
        },
    }

    for _, tt := range tests {
        t.Run(tt.name, func(t *testing.T) {
            got, err := Calculate(tt.input)
            if (err != nil) != tt.wantErr {
                t.Errorf("Calculate() error = %v, wantErr %v", err, tt.wantErr)
                return
            }
            if !reflect.DeepEqual(got, tt.want) {
                t.Errorf("Calculate() = %v, want %v", got, tt.want)
            }
        })
    }
}

Step 3: Run Tests (RED)

go test -v ./...

Step 4: Implement (GREEN)

func Calculate(input Input) (Output, error) {
    // Minimal implementation
}

Step 5: Benchmark

func BenchmarkCalculate(b *testing.B) {
    input := Input{...}
    for i := 0; i < b.N; i++ {
        Calculate(input)
    }
}

Go Testing Commands

# Run all tests
go test ./...

# Run with verbose output
go test -v ./...

# Run with coverage
go test -cover ./...

# Run with race detector
go test -race ./...

# Run benchmarks
go test -bench=. ./...

# Generate coverage report
go test -coverprofile=coverage.out ./...
go tool cover -html=coverage.out

Read the full file on GitHub · 132 lines

Changes

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.

  1. 9d ago First seen · 132 lines · 8 tokens per session scan A ff270caf17e4

Subscribe to this mod's changes

go-test is a command published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed 5d ago), licensed MIT. It adds 8 tokens to every session and 638 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to go-test, differing in 0 lines, and is treated as a copy.