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 wangke19/gemini-ai-helpers --skill lang-gogit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/lang-go)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/lang-go"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/lang-go/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/wangke19/gemini-ai-helpers/lang-go"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/lang-go.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.00022 | $0.00587 |
| Opus 5 | $0.00011 | $0.00293 |
| Sonnet 5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
Go Language 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 10d 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.
This is a copy
95% identical to go-code-review — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Language Review
This skill provides Go-specific guidance for code quality reviews. It is loaded automatically by the pre-commit-review command when --language go is specified or when .go files are detected among the changed files.
When to Use This Skill
Use this skill when reviewing Go source code. Its sections are referenced during the unit test coverage, idiomatic code, and build verification review steps.
Test Conventions
- Table-driven tests: Prefer table-driven tests for functions with multiple input/output combinations
- Subtests: Use
t.Run()for subtests to provide clear test case identification - Parallel tests: Use
t.Parallel()at the top of test functions and subtests where tests are independent - Race detection: Tests must be compatible with the
-raceflag — avoid shared mutable state between parallel tests - File co-location: Test files must be co-located with source files using the
_test.gosuffix - Test helpers: Use
t.Helper()in test helper functions so failure messages report the caller's line number - Behavior-focused: Test names should describe behavior, not implementation. Test both success and error paths
Idiomatic Go
Follow the conventions in Effective Go and the Go Code Review Comments wiki. Key reminders:
- Formatting: All code must be formatted with
gofmt. Unformatted code is a blocking issue - Naming: Use
MixedCaps/mixedCaps. Avoid stuttering (http.Servernothttp.HTTPServer). Acronyms are all caps (URL,HTTP,ID) - Error handling: Check every error. Wrap with
fmt.Errorf("context: %w", err)to preserve the chain forerrors.Is()/errors.As() - Interfaces: Keep interfaces small. Accept interfaces, return concrete types
- Early returns: Handle error cases first; keep the happy path at the lowest indentation level
- Context: Pass
context.Contextas the first parameter to functions that perform I/O or may be long-running
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.
- 10d ago First seen · 42 lines · 22 tokens per session scan A a1e044e43b01
Go Language Review is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 587 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to go-code-review, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
otel-go-reviewer
Review pull requests, diffs, patches, or design proposals for the open-telemetry/opentelemetry-go repository with a senior maintainer mindset. Use when changes in opentelemetry-go may affect OpenTelemetry specification compliance, repository contribution rules, changelog requirements, module versioning boundaries, API…
opentelemetry-go-reviewer
High-bar review for changes in open-telemetry/opentelemetry-go with strict standards for correctness, compatibility, and performance.
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.
context-lifecycle
Review goroutines, timers, callbacks, actor handoffs, and async cleanup for context lifetime bugs. Use when code starts work that may outlive the caller, especially from RPC handlers, wallet startup, daemon startup, actors, or notification registrations.