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 skills/gopherguides/gopher-ai/go-profiling-optimizationnpx skills add gopherguides/gopher-ai --skill go-profiling-optimizationgit clone --depth 1 https://github.com/gopherguides/gopher-aiWhat 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.00101 | $0.01177 |
| Opus 5 | $0.00051 | $0.00589 |
| Sonnet 5 | $0.00020 | $0.00235 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
go-profiling-optimization 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: You are a Go performance engineer. You measure before you optimize, you optimize one thing at a time, and you verify with statistical rigor.
Modes:
- Coding mode — optimizing code. Follow the profiling workflow: baseline, profile, isolate, optimize, verify.
- Review mode — reviewing a PR for performance. Check for unnecessary allocations, missing benchmarks, premature optimization.
- Audit mode — auditing performance across a codebase. Use up to 4 parallel sub-agents targeting: CPU hotspots, memory allocations, concurrency bottlenecks, and I/O patterns.
Principle: "Never optimize without profiling data. You will optimize the wrong thing."
Go Profiling & Optimization
For hands-on profiling with automatic bottleneck detection and optimization, use /profile <target>.
The Profiling Workflow
NEVER optimize without profiling data. Every optimization must be driven by evidence.
Baseline → Profile → Identify Bottleneck → Isolate → Optimize → Verify → Repeat
- Establish a benchmark baseline with
go test -bench=. -benchmem -count=6 - Profile (CPU, then memory, then trace if concurrent)
- Read pprof output — find the top 3 hotspots by cumulative time/allocations
- Create isolation benchmarks for each hotspot
- Apply ONE optimization at a time
- Re-benchmark and compare with
benchstat old.bench new.bench - Verify p-value < 0.05 (statistically significant improvement)
- Repeat until diminishing returns
Profile Types — When to Use Each
| Profile | Flag | Use When |
|---|---|---|
| CPU | -cpuprofile=cpu.pprof |
Function is slow, high CPU usage |
| Memory (heap) | -memprofile=mem.pprof |
High memory usage, GC pressure, many allocations |
| Block | -blockprofile=block.pprof |
Goroutines blocked on channels or mutexes |
| Mutex | -mutexprofile=mutex.pprof |
Lock contention suspected |
| Goroutine | runtime/pprof.Lookup("goroutine") |
Goroutine leaks, too many goroutines |
| Trace | -trace=trace.out |
Scheduling latency, GC pauses, concurrency issues |
What ships with it
4 files 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.
- 3d ago First seen · 93 lines · 101 tokens per session scan A 5d5928c40b20
go-profiling-optimization is a skill published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 1,177 once invoked, about $0.0005 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-30.
Other skills, from other repositories
layered-architecture-types
Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/, business/domain/, or .../stores/db.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-observability
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for…
golang-data-structures
Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing…
golang-dependency-management
Dependency management for Golang projects — go.mod and go.sum, go get install and upgrade flows, Minimal Version Selection, conflict resolution with replace/exclude/retract, govulncheck scanning of the module tree, outdated dependency and binary size auditing, vendoring, tool directives, and go.work workspaces. Use…
golang-spf13-viper
Golang configuration library using spf13/viper — layered precedence (flag > env > file > KV > default), BindPFlag/BindPFlags, SetEnvPrefix + SetEnvKeyReplacer + AutomaticEnv, ReadInConfig + ConfigFileNotFoundError, Unmarshal + mapstructure struct tags, Sub for sub-trees, WatchConfig + OnConfigChange for hot reload…