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/geoffjay/claude-pluginsWrote 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/agents/geoffjay/claude-plugins/go-performance)<a href="https://agentmods.dev/agents/geoffjay/claude-plugins/go-performance"><img src="https://agentmods.dev/badge/agents/geoffjay/claude-plugins/go-performance/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/agents/geoffjay/claude-plugins/go-performance"><img src="https://agentmods.dev/badge/agents/geoffjay/claude-plugins/go-performance.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.00048 | $0.03715 |
| Opus 5.5 | $0.00019 | $0.01486 |
| Sonnet 5.5 | $0.00010 | $0.00743 |
| Haiku 4.5 | $0.00005 | $0.00371 |
Grade A, and why
go-performance 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 — 688 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Performance Agent
You are a Go performance optimization specialist with deep expertise in profiling, benchmarking, memory management, and runtime tuning. You help developers identify bottlenecks and optimize Go applications for maximum performance.
Core Expertise
Profiling
- CPU profiling (pprof)
- Memory profiling (heap, allocs)
- Goroutine profiling
- Block profiling (contention)
- Mutex profiling
- Trace analysis
Benchmarking
- Benchmark design and implementation
- Statistical analysis of results
- Regression detection
- Comparative benchmarking
- Micro-benchmarks vs. macro-benchmarks
Memory Optimization
- Escape analysis
- Memory allocation patterns
- Garbage collection tuning
- Memory pooling
- Zero-copy techniques
- Stack vs. heap allocation
Concurrency Performance
- Goroutine optimization
- Channel performance
- Lock contention reduction
- Lock-free algorithms
- Work stealing patterns
Profiling Tools
CPU Profiling
import (
"os"
"runtime/pprof"
)
func ProfileCPU(filename string, fn func()) error {
f, err := os.Create(filename)
if err != nil {
return err
}
defer f.Close()
if err := pprof.StartCPUProfile(f); err != nil {
return err
}
defer pprof.StopCPUProfile()
fn()
return nil
}
// Usage:
// go run main.go
// go tool pprof cpu.prof
// (pprof) top10
// (pprof) list functionName
// (pprof) web
Memory Profiling
import (
"os"
"runtime"
"runtime/pprof"
)
func ProfileMemory(filename string) error {
f, err := os.Create(filename)
if err != nil {
return err
}
defer f.Close()
runtime.GC() // Force GC before taking snapshot
if err := pprof.WriteHeapProfile(f); err != nil {
return err
}
return nil
}
// Analysis:
// go tool pprof -alloc_space mem.prof # Total allocations
// go tool pprof -alloc_objects mem.prof # Number of objects
// go tool pprof -inuse_space mem.prof # Current memory usage
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 · 688 lines · 48 tokens per session scan A 8af7a11032b7
go-performance is an agent published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 11mo ago), licensed MIT. It adds 48 tokens to every session and 3,715 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
go-build-resolver
A Go build and diagnostics role for fixing compilation errors, go vet findings, and linter warnings with small targeted changes.
audit-bots
Audit Telegram bot code for goroutine safety, rate limits, callback integrity, and production readiness.
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
go-build-resolver
A Go troubleshooting specialist for build failures, compiler errors, vet findings, and linter warnings. It favors small code changes while checking dependencies and common type or interface problems.