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/mfmezger/ai_agent_dotfiles/go-engineeringnpx skills add mfmezger/ai_agent_dotfiles --skill go-engineeringgit clone --depth 1 https://github.com/mfmezger/ai_agent_dotfilesWrote 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/mfmezger/ai_agent_dotfiles/go-engineering)<a href="https://agentmods.dev/skills/mfmezger/ai_agent_dotfiles/go-engineering"><img src="https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/go-engineering.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.00096 | $0.00837 |
| Opus 5 | $0.00048 | $0.00418 |
| Sonnet 5 | $0.00019 | $0.00167 |
| Haiku 4.5 | $0.00010 | $0.00084 |
Grade A, and why
go-engineering 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 6d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Engineering
Produce Go that is small in surface area, explicit in behavior, and easy to read under review. Prefer straightforward package boundaries, concrete types first, small interfaces where they help callers, explicit error handling, and concurrency that can be reasoned about.
Workflow
- Identify the package boundary. Library: optimize for small exports, concrete behavior, and compatibility. Application: optimize for operability, wiring clarity, and cancellation-aware execution.
- Model the package API before adding helpers. Keep exported identifiers minimal and make zero values useful when practical.
- Choose concrete types first. Introduce interfaces where consumers benefit, not as a reflex.
- Design error flow early.
Wrap with context, support
errors.Isanderrors.As, and keep sentinel errors narrow. - Add concurrency only where it simplifies latency or throughput. Cancellation, shutdown, ownership, and goroutine lifetime must be explicit.
- Verify before finalizing.
Run
gofmt,go test ./..., andgo vet ./...when appropriate. Addgo test -race ./...for concurrency-sensitive code. Keep examples and benchmarks honest.
Load References By Need
| Need | Reference |
|---|---|
| Package layout, modules, exported API shape, CLI/app structure | references/workflow.md |
| Errors, wrapping, sentinels, concrete types vs interfaces | references/api-and-errors.md |
| Concurrency, channels, contexts, goroutines, shutdown | references/concurrency.md |
| Testing, table tests, fuzzing, benchmarks, temp dirs | references/testing-and-quality.md |
| Performance, allocations, slices, maps, common footguns | references/performance-and-footguns.md |
Default Standards
- Keep packages focused and exports intentional.
- Start with concrete types; accept interfaces when they improve the consuming code.
- Pass
context.Contextexplicitly for request-scoped or cancelable work. - Return errors, wrap them with context, and avoid panic for ordinary failures.
- Prefer simple loops and data flow over abstraction-heavy “framework” patterns.
- Keep goroutine ownership clear. Every goroutine should have a reason to exit.
- Make the zero value useful when practical and not misleading.
What ships with it
5 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.
- 6d ago First seen · 65 lines · 96 tokens per session scan A ac743c92ac73
go-engineering is a skill published in the GitHub repository mfmezger/ai_agent_dotfiles (5 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 837 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
golang-patterns
Idiomatic Go patterns covering error handling, interfaces, goroutines, channels, testing, and common pitfalls. Activate when writing or reviewing Go code.
go-clean-architecture
Use when scaffolding or refactoring a Go service into a framework-agnostic clean (hexagonal) architecture: Domain, Usecase, Repository, Delivery layers, inward dependency rule, 'framework/database is a detail'. Apply when untangling a monolith or checking whether business logic is testable without HTTP or DB.
go-code-review
Invoke this skill to systematically review a Go change against community style standards before merging. Walks the diff topic by topic — formatting, errors, naming, concurrency, interfaces, data structures, security, declarations, functions, style, logging, imports, generics, testing — flagging issues with line…
go-code-style
Use when writing or reviewing Go code for clarity, formatting, control flow, variable declarations, switch usage, and function design. Covers the priority order (clarity > simplicity > concision > maintainability > consistency), gofmt rules, early-return / no-else patterns, switch over if-else chains, slice/map…
go-concurrency
Use when writing or reviewing concurrent Go code — goroutines, channels, select, mutexes, atomics, errgroup, singleflight, worker pools, or fan-out/fan-in pipelines. Apply proactively whenever a goroutine is spawned, a shared field is mutated, or a channel is created, even if the user has not asked about concurrency.…
go-data-structures
Use when choosing or operating on Go slices, maps, arrays, strings, or container/ types — including slice internals, capacity growth, preallocation, map buckets, sets via map[T]struct{}, strings.Builder vs bytes.Buffer, generic containers, and the slices/maps standard packages (Go 1.21+). Apply proactively whenever…