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 skills add johnqtcg/awesome-skills --skill go-performance-reviewgit clone --depth 1 https://github.com/johnqtcg/awesome-skillsWrote 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/skills/johnqtcg/awesome-skills/go-performance-review)<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/go-performance-review"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/go-performance-review/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/skills/johnqtcg/awesome-skills/go-performance-review"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/go-performance-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.02865 |
| Opus 5 | $0.00040 | $0.01432 |
| Sonnet 5 | $0.00016 | $0.00573 |
| Haiku 4.5 | $0.00008 | $0.00286 |
Grade A, and why
go-performance-review 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 11d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Performance Review
Purpose
Identify performance issues and resource inefficiency in Go code. This skill exists because performance findings are almost all Medium severity and get systematically crowded out when mixed with High-severity Security/Concurrency findings.
Important distinction: lock contention is performance (here); race condition is concurrency (go-concurrency-review).
This skill does NOT cover: security, concurrency correctness, code style, test quality, error handling, or business logic — those belong to sibling vertical skills.
When To Use
- Code contains
make([]T, ...)ormake(map[K]V, ...) - Code builds strings in loops
- Code queries DB/Redis inside loops
- Code configures connection pools or HTTP clients
- Code runs on hot paths (per-request, high-frequency)
When NOT To Use
- Security vulnerabilities →
go-security-review - Race conditions, goroutine leaks →
go-concurrency-review - Code style/lint →
go-quality-review - Error handling →
go-error-review
Mandatory Gates
1) Go Version Gate
Read go.mod. Key: strings.Clone (1.20+), slices.Clone (1.21+).
2) Anti-Example Suppression Gate
MUST quote specific evidence. Category match alone insufficient.
Embedded anti-examples:
- "Should pre-allocate slice" — when slice is small (<16 elements) or size is truly unknown at creation time. Must cite evidence the slice is large and size is known.
- "Should use sync.Pool" — when object is small and allocated infrequently (cold path, startup, config).
- "Struct fields should be reordered" — when struct has <4 fields or alignment savings <8 bytes.
- "Should use strings.Clone" — when both substring and parent are short-lived locals in same GC scope.
- "Add Count-First guard" — when the business domain guarantees the query always returns rows (e.g., seeded reference data, system-level lookups). Must cite evidence that total==0 is impossible in practice.
- Hot-path rule: Do NOT flag performance issues in cold-path code (startup, one-time init, config loading, test setup, CLI argument parsing). Must cite evidence of hot-path execution: "called per HTTP request", "inside for loop over N items", "in handler serving N QPS".
What ships with it
3 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.
- 11d ago First seen · 185 lines · 80 tokens per session scan A 1592ed33480e
go-performance-review is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 2,865 once invoked, about $0.0004 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
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
go-concurrency-reviewer
Audit Go concurrency — goroutines, channels, mutexes, context propagation, race conditions.
go-error-reviewer
Deep audit of Go error handling — wrapping, inspection, logging, panic/recover patterns.
go-modernizer
Detect outdated Go patterns and suggest modern idioms — Go 1.21 through 1.24+ features.