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-concurrency-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-concurrency-review)<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/go-concurrency-review"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/go-concurrency-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-concurrency-review"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/go-concurrency-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.00067 | $0.02698 |
| Opus 5 | $0.00034 | $0.01349 |
| Sonnet 5 | $0.00013 | $0.00540 |
| Haiku 4.5 | $0.00007 | $0.00270 |
Grade A, and why
go-concurrency-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 12d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Concurrency Review
Purpose
Identify concurrency defects and goroutine lifecycle issues in Go code. Scope: race conditions, deadlocks, goroutine leaks, mutex misuse, context propagation, and lifecycle management.
This skill does NOT cover: security vulnerabilities, performance optimization, code style, test quality, error handling patterns, or business logic — those belong to sibling vertical skills.
When To Use
- Code contains
go func, goroutine creation - Code uses channels,
syncprimitives (Mutex, RWMutex, WaitGroup) - Code uses
errgroup,singleflight - Code involves context propagation and cancellation
- Code contains graceful shutdown logic
When NOT To Use
- Security vulnerabilities →
go-security-review - Performance optimization (lock contention as perf issue) →
go-performance-review - Code style/lint →
go-quality-review - Error handling correctness →
go-error-review - Business logic →
go-logic-review
Mandatory Gates
1) Execution Integrity Gate
Never claim go test -race ran unless it actually produced output. If not run: state reason + exact command.
2) Go Version Gate
Read go.mod for go directive. Key version gates:
errgroup.SetLimit(Go 1.20+)sync.OnceValue/sync.OnceFunc(Go 1.21+)- Loop variable fix (Go 1.22+) — do NOT flag loop variable capture in Go ≥ 1.22
3) Anti-Example Suppression Gate
MUST quote specific code evidence satisfying precondition. Category match alone insufficient.
Embedded anti-examples:
- "Race condition on this map" — when map is created and consumed within single function scope or single goroutine. Cite the creation site and all access sites to confirm single-goroutine usage.
- "Should use errgroup instead of WaitGroup" — when no error propagation is needed and goroutine count is small and fixed (e.g., 2-3 known goroutines).
- "Missing context propagation" — when function is synchronous, short-lived, performs no I/O, and has no cancellable work.
- "Loop variable capture bug" — when project uses Go ≥ 1.22 (check go.mod). The loop variable fix makes
v := vunnecessary. - "Should add mutex" — when data structure is only written during initialization (before any goroutine launch) and only read afterward.
What ships with it
2 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.
- 12d ago First seen · 193 lines · 67 tokens per session scan A 066d2731552f
go-concurrency-review is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 2,698 once invoked, about $0.0003 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.