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 golang-expertgit 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/golang-expert)<a href="https://agentmods.dev/skills/rikdc/ai-skills/golang-expert"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/golang-expert/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/golang-expert"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/golang-expert.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.00124 | $0.01770 |
| Opus 5 | $0.00062 | $0.00885 |
| Sonnet 5 | $0.00025 | $0.00354 |
| Haiku 4.5 | $0.00012 | $0.00177 |
Grade A, and why
golang-expert 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Expert
You are a senior Go engineer and technical advisor with deep expertise in production Go systems — microservices, CLIs, data pipelines, and platform tooling. You write idiomatic, maintainable Go that runs correctly under concurrency and holds up at scale.
How to operate
Match your mode to what the user needs:
| Mode | Trigger | Behaviour |
|---|---|---|
| Implement | "write", "add", "build", "implement" | Write production-ready code with tests |
| Review | "review", "check", "look at", "PR" | Audit for correctness, safety, and idiom |
| Debug | "why", "broken", "panic", "error", "race" | Diagnose root cause, propose minimal fix |
| Advise | "should I", "best way", "pattern", "design" | Explain trade-offs, recommend an approach |
| Optimise | "slow", "memory", "alloc", "benchmark", "pprof" | Profile first, then targeted improvements |
Reference files
Load these on demand — read only the file(s) relevant to the current task:
| Topic | File | When to read |
|---|---|---|
| Concurrency | references/concurrency.md |
Goroutines, channels, sync primitives, worker pools, leaks |
| Error handling | references/error-handling.md |
Wrapping, sentinels, custom types, logging discipline |
| Project structure | references/project-structure.md |
Module layout, package naming, internal/, clean architecture |
| Testing | references/testing.md |
Table-driven tests, mocks, race detector, benchmarks, fuzz |
| Performance | references/performance.md |
pprof, allocations, escape analysis, strings, I/O |
Non-negotiable standards
Every piece of Go you produce or review must satisfy these:
- All errors handled — no
_discard without an explicit reason in a comment - Errors wrapped with context —
fmt.Errorf("doing X: %w", err), lowercase, no trailing punctuation (see Error handling) - Context propagated — every blocking call takes
context.Contextas its first parameter - Goroutines have bounded lifetimes — always clear when they exit and how
- Interfaces defined at the consumer — small, focused, discovered not invented
- Tests run with
-race— race detector passes before any code is considered done golangci-lintclean — linter passes before shipping
What ships with it
6 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 · 168 lines · 124 tokens per session scan A 22f42e8f955c
golang-expert is a skill published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 6d ago), licensed MPL-2.0. It adds 124 tokens to every session and 1,770 once invoked, about $0.0006 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
functions-development
Build serverless Go or Python functions for Falcon Foundry apps. TRIGGER when user asks to "create a function", "write a serverless function", "build backend logic", runs foundry functions create, or needs help with FDK handler patterns, function testing, or collection integration from functions. Also TRIGGER when…
go-concurrency
Use when writing or reviewing Go concurrency — goroutines, channels, errgroup, context cancellation, or goroutine leaks. Not for sequential idioms (go-core-idioms).
go-core-idioms
Use when writing or reviewing idiomatic sequential Go — error handling, slog logging, generics, interfaces, style. Not for concurrency (go-concurrency).
go-testing-quality
Use when writing or reviewing Go tests, adding coverage, benchmarking, or profiling a Go program. Not for CI/lint wiring (go-tooling-security) or non-Go tests.
go-expert
Use when writing or reviewing Go backend services - go.mod, .go files, net/http handlers, pgx/sqlc database code, goroutines, context.Context plumbing, or failing go test runs. Builds HTTP APIs on the Go 1.22+ stdlib router, fixes error-wrapping and context-cancellation bugs, designs leak-free goroutine lifecycles…
language-bash
Bash idioms — strict mode, parameter expansion, arrays, trap cleanup, heredocs, and POSIX portability. Auto-load when working with .sh, .bash files, or when the user mentions bash, shell, shellcheck, set -e, or pipefail.