A command for measuring Go performance, finding bottlenecks, applying targeted changes, and comparing results before and after optimization.

Use it to profile a function, file, package, or current project with benchmarks, CPU and memory profiles, and execution traces where needed.

It ensures performance work is based on profiling data and statistical comparisons instead of assumptions.

profile — Command by gopherguides

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.

agentmods

npx agentmods add commands/gopherguides/gopher-ai/profile

Clone the repo

git clone --depth 1 https://github.com/gopherguides/gopher-ai

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,605 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5	$0.00014	$0.01605
Opus 5	$0.00007	$0.00803
Sonnet 5	$0.00003	$0.00321
Haiku 4.5	$0.00001	$0.00161

Measured 2d ago against content hash 701167a66b9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

plugins/go-dev/commands/profile.md · 141 lines

How it starts

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

If $ARGUMENTS is empty or not provided:

Usage: /profile <target>

Examples:

/profile ./pkg/auth/ — profile all benchmarkable code in a package
/profile ProcessOrder — profile a specific function
/profile . — profile the current package

Workflow: baseline → CPU profile → memory profile → trace (if concurrent) → rank bottlenecks → optimize one at a time and verify with benchstat → final before/after comparison.

Ask: "What file, function, or package would you like me to profile?"

If $ARGUMENTS is provided:

Profile Go code, identify bottlenecks, apply optimizations, and verify improvements with statistical rigor. Systematic profile → isolate → optimize → verify cycle.

Loop Initialization

!if [ ! -x "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" ]; then echo "ERROR: Plugin cache stale. Run /gopher-ai-refresh (or refresh-plugins.sh) and restart Claude Code."; exit 1; else "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" "profile" "COMPLETE"; fi

Configuration

Target: $ARGUMENTS (file, function, or package)

IRON LAW: NEVER OPTIMIZE WITHOUT PROFILING DATA FIRST

Do not guess. Do not "just try changing X." Every optimization must be preceded by profiling data showing WHERE the bottleneck actually is. Measure before AND after every change.

Phase 1: Environment & Baseline

Check tooling:

which benchstat 2>/dev/null && echo "benchstat: available" || echo "benchstat: NOT FOUND"
go version

Install benchstat if missing: go install golang.org/x/perf/cmd/benchstat@latest

Locate target code — read it, identify hot path, note concurrency and I/O patterns.
Find or create benchmarks:
```
rg -l 'func Bench' --glob '*_test.go' ./target/path/ 2>/dev/null
```
If none found: generate table-driven benchmarks with b.ReportAllocs(), realistic inputs, sink variables, b.StopTimer()/b.StartTimer() around setup. Follow the /bench patterns.

Establish baseline:

go test -bench=. -benchmem -count=6 -run=^$ ./target/path/ 2>&1 | tee .profile-baseline.bench
benchstat .profile-baseline.bench

If variance >5%, increase -count or investigate environment noise.

Read the full file on GitHub · 141 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.

2d ago First seen · 141 lines · 14 tokens per session scan A 701167a66b9e

Subscribe to this mod's changes

profile is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 1,605 once invoked, about $0.0001 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.

Analytics and metrics Go Languages

profile

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Loop Initialization

Configuration

IRON LAW: NEVER OPTIMIZE WITHOUT PROFILING DATA FIRST

Phase 1: Environment & Baseline

What this file has done since we first saw it

Other commands, from other repositories

trex.kind.add-field

trex.verify

trex.test.unit

go-build

go-review

cli-patterns