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 agentmods add skills/gvre/skills/go-developernpx skills add gvre/skills --skill go-developergit clone --depth 1 https://github.com/gvre/skillsWhat 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 | $0.00097 | $0.05624 |
| Opus 5 | $0.00048 | $0.02812 |
| Sonnet 5 | $0.00019 | $0.01125 |
| Haiku 4.5 | $0.00010 | $0.00562 |
Grade A, and why
go-developer 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 2d 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 — 546 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Developer
Guide for writing production-quality Go 1.25+ projects following current best practices.
Structure: This file contains rules, guidelines, and compact examples. For full code examples and deep dives, see the files in
references/. Consult them when you need implementation details beyond what's shown here.
Version Support
This guide covers:
- Go 1.25+: Base requirements and common features (all sections below)
- Go 1.25: Runtime, tooling, and stdlib improvements → See references/go-1.25-features.md
- Go 1.26: Language changes, GC improvements, new packages → See references/go-1.26-features.md
Feature Version Matrix
| Feature | 1.25 | 1.26 |
|---|---|---|
| Container-aware GOMAXPROCS | ✅ | ✅ |
sync.WaitGroup.Go() |
✅ | ✅ |
testing/synctest (stable) |
✅ | ✅ |
go doc -http=:6060 |
✅ | ✅ |
go.mod ignore directive |
✅ | ✅ |
| Green Tea GC (default) | ❌ (experimental) | ✅ |
new(expr) initialization |
❌ | ✅ |
| Self-referential generic types | ❌ | ✅ |
errors.AsType |
❌ | ✅ |
Rewritten go fix with modernizers |
❌ | ✅ |
pprof flame graphs by default |
❌ | ✅ |
Quick Reference
Core Requirements (1.25+):
- Go 1.25+ minimum
- Use
go.modfor all dependency management golangci-lintfor lintinggovulncheckfor vulnerability scanning- Table-driven tests with
t.Run - Interfaces for dependency injection
- Explicit error handling (no panics for expected errors)
Project Overrides
How tool settings are resolved depends on the task:
- Reviewing existing code / PRs: Read
go.mod(for go-version) and.golangci.yml(for linter configuration) from the repository. The project's actual configuration is the source of truth. Do not override what the project already defines. - Creating new projects: Use the defaults below when no
go.modexists yet.
Local overrides (see "What Can Be Overridden") apply in both modes and take precedence over both the project config and the defaults below.
What ships with it
7 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.
- 2d ago First seen · 546 lines · 97 tokens per session scan A aef9944922a5
go-developer is a skill published in the GitHub repository gvre/skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 97 tokens to every session and 5,624 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.