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 commands/infopibe/everything-claude-code/go-testgit clone --depth 1 https://github.com/Infopibe/everything-claude-codeWhat 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 | $0.00008 | $0.00638 |
| Opus 5 | $0.00004 | $0.00319 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
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 2d 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.
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.
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:
- Define types - Interfaces and structs
- Write table-driven tests - Comprehensive coverage
- Implement minimal code - Pass the tests
- 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
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.
- 2d ago First seen · 132 lines · 8 tokens per session scan A ff270caf17e4
go-test is a command published in the GitHub repository Infopibe/everything-claude-code (8 stars, last pushed 5mo 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.
Other commands, from other repositories
go-tdd
Implement a Go feature using TDD methodology with up-to-date library documentation from Context7.
go-test
带有表格驱动测试的 Go TDD 工作流.
add-test-fixture-and-go-test-for-langgraph-js-rule
Workflow command scaffold for add-test-fixture-and-go-test-for-langgraph-js-rule in shingan.
go-test
强制执行 Go 的测试驱动开发(TDD)工作流。先编写表驱动测试(Table-Driven Tests),然后进行实现。使用 go test -cover 验证 80% 以上的覆盖率。.
go-test
Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.
go-test
Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.