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 FutureJJ/claude-skills --skill go-engineergit clone --depth 1 https://github.com/FutureJJ/claude-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/futurejj/claude-skills/go-engineer)<a href="https://agentmods.dev/skills/futurejj/claude-skills/go-engineer"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/go-engineer.svg" alt="Measured on agentmods" 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.00047 | $0.00291 |
| Opus 5 | $0.00023 | $0.00146 |
| Sonnet 5 | $0.00009 | $0.00058 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
go-engineer 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 7d 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.
What it actually says
Go Engineer
You are a Go expert who writes idiomatic, concurrent, and well-tested Go code.
Core Principles
- Accept interfaces, return structs. Functions should depend on behavior, not concrete types.
- Errors are values. Handle them explicitly. Use
fmt.Errorfwith%wfor wrapping. - Don't communicate by sharing memory; share memory by communicating. Use channels.
- Make the zero value useful. Design types so their zero value is ready to use.
Anti-Patterns
- Goroutine leaks — always ensure goroutines can exit
- Channel deadlocks — prefer buffered channels for known producers
- Interface pollution — don't define interfaces you don't need yet
- Panic for error handling — panic is for programmer errors, not runtime errors
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Concurrency | references/concurrency.md |
Goroutines, channels, sync, patterns |
| Error handling | references/errors.md |
Error wrapping, sentinel errors, custom types |
| Project structure | references/structure.md |
Layout, packages, testing |
What ships with it
3 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.
- 7d ago First seen · 31 lines · 47 tokens per session scan A 2a0c7db2d4c8
go-engineer is a skill published in the GitHub repository FutureJJ/claude-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 291 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
go-best-practices
Use when reading or writing Go files (.go, go.mod).
swift-networking
Builds a protocol-based async/await networking layer with URLSession, testable abstractions, error handling, and mock support for Swift projects. Use when user says "add networking", "create an API layer", "fetch data from API", "build a network service", "add URLSession", "implement HTTP requests", "create a REST…
swift-project-setup
Bootstraps a new Swift/SwiftUI/UIKit project with MVVM architecture, standard folder structure, testing targets, and CLAUDE.md configuration. Use when user says "create a new project", "setup a new app", "start a new iOS project", "scaffold a Swift project", "initialize an Xcode project", or "new SwiftUI app".
qa-go
Go testing skill with table-driven tests, httptest, testify, and integration testing patterns. Use when writing or running Go backend tests.
golang
Golang backend development skill for REST APIs with Chi router, PostgreSQL, and layered architecture. Use when implementing Go backend code.
golang-pro
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming…