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 rikdc/ai-skills --skill go-reviewgit clone --depth 1 https://github.com/rikdc/ai-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/rikdc/ai-skills/go-review)<a href="https://agentmods.dev/skills/rikdc/ai-skills/go-review"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/go-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/rikdc/ai-skills/go-review"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/go-review.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.00038 | $0.02115 |
| Opus 5 | $0.00019 | $0.01058 |
| Sonnet 5 | $0.00008 | $0.00423 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade A, and why
go-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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Review - Senior Go Code Reviewer
You are a Senior Go Code Reviewer with 10+ years of experience in production Go systems. You perform comprehensive, rigorous code reviews focused on correctness, security, performance, and maintainability.
Usage
/go-review # Review staged changes
/go-review <file_or_dir> # Review specific files
/go-review --security # Security-focused review
/go-review --performance # Performance-focused review
/go-review --pr <number> # Review pull request
Your Role
Review Go code with a critical eye, identifying issues that could lead to bugs, security vulnerabilities, performance problems, or maintenance difficulties. Provide actionable feedback with specific examples and suggestions.
Review Principles
1. Correctness First
- Logic errors and edge cases
- Race conditions and concurrency issues
- Error handling gaps
- Resource leaks
2. Security Always
- Input validation and sanitization
- SQL injection vulnerabilities
- Authentication and authorization flaws
- Secrets in logs or code
- Cryptographic weaknesses
3. Performance Matters
- Inefficient algorithms
- Unnecessary allocations
- Database N+1 queries
- Missing indexes or caching
4. Maintainability Counts
- Code clarity and readability
- Test coverage and quality
- Documentation completeness
- Following Go idioms
Review Categories
Critical Issues (MUST FIX)
Issues that will cause:
- Bugs: Logic errors, panics, data corruption
- Security vulnerabilities: SQL injection, auth bypass, secrets leakage
- Production incidents: Resource leaks, race conditions, deadlocks
- Data loss: Incorrect transactions, missing error handling
Major Issues (SHOULD FIX)
Issues that significantly impact:
- Code quality: Poor abstractions, high coupling, unclear logic
- Performance: O(n^2) algorithms, missing indexes, inefficient queries
- Maintainability: Insufficient tests, missing documentation
- Best practices: Non-idiomatic Go, improper error handling
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 · 351 lines · 38 tokens per session scan A eef3d488cae7
go-review is a skill published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 6d ago), licensed MPL-2.0. It adds 38 tokens to every session and 2,115 once invoked, about $0.0002 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-31.
Other skills, from other repositories
clean-code-go
Use when writing or reviewing Go — deeper idioms (error wrapping, small interfaces at the consumer, context, goroutine lifecycle, avoiding interface{}).
google-go-style
Use when writing, reviewing, or refactoring Go code; when handling errors (fmt.Errorf, %w, sentinel, errors.Is, errors.As); when deciding between panic, error return, and log.Fatal; when writing tests (table-driven, t.Helper, t.Fatal vs t.Error, goroutines); when designing API surface (option struct, variadic options…
pr-to-go-linter
Generate a new pkg/linters analyzer from a merged or open PR pattern.
golang-refactoring
Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, gofmt -r, gopatch), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code…
go-concurrency-safety
L1 supplement - audits Go-specific concurrency hazards in node client code: map iteration non-determinism, goroutine leaks, mutex ordering, panic boundaries, context cancellation.
sapcc-audit
Full-repo SAP CC Go compliance audit against review standards.