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/dallay/agents-skills/go-developmentnpx skills add dallay/agents-skills --skill go-developmentgit clone --depth 1 https://github.com/dallay/agents-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/dallay/agents-skills/go-development)<a href="https://agentmods.dev/skills/dallay/agents-skills/go-development"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/go-development.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 | $0.00050 | $0.02685 |
| Opus 5 | $0.00025 | $0.01342 |
| Sonnet 5 | $0.00010 | $0.00537 |
| Haiku 4.5 | $0.00005 | $0.00268 |
Grade A, and why
go-development 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 4d 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 — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Development
Production patterns and idioms for Go programming, covering project structure, error handling, concurrency, interfaces, testing, and module management.
When to Use This Skill
- Starting or structuring a Go project
- Writing idiomatic Go error handling
- Working with goroutines and channels
- Designing interfaces and composable packages
- Writing tests with
go test - Managing dependencies with Go modules
- Using context for cancellation and propagation
Core Concepts
1. Project Layout
myapp/
├── cmd/
│ └── myapp/
│ └── main.go # Entry point
├── internal/ # Private packages (not importable externally)
│ ├── handler/
│ │ └── handler.go
│ ├── service/
│ │ └── service.go
│ └── repository/
│ └── repository.go
├── pkg/ # Public reusable packages
│ └── httputil/
│ └── response.go
├── go.mod
├── go.sum
├── Makefile
└── README.md
2. Key Principles
| Principle | Go Idiom |
|---|---|
| Error handling | Return error as last value, check immediately |
| Composition | Embed interfaces, not structs |
| Concurrency | Share memory by communicating (channels) |
| Simplicity | Fewer abstractions, explicit over implicit |
| Zero values | Design types so zero value is useful |
Quick Start
# Initialize a new module
go mod init github.com/user/myapp
# Add dependencies
go get github.com/gin-gonic/gin@latest
# Tidy dependencies
go mod tidy
# Build and run
go build -o myapp ./cmd/myapp
go run ./cmd/myapp
# Run tests
go test ./...
go test -v -race -count=1 ./...
Patterns
Pattern 1: Error Handling
package service
import (
"errors"
"fmt"
)
// Define sentinel errors for comparison
var (
ErrNotFound = errors.New("not found")
ErrUnauthorized = errors.New("unauthorized")
)
// Custom error type with context
type ValidationError struct {
Field string
Message string
}
func (e *ValidationError) Error() string {
return fmt.Sprintf("validation failed on %s: %s", e.Field, e.Message)
}
// Wrap errors with context using %w
func GetUser(id string) (*User, error) {
user, err := db.Find(id)
if err != nil {
return nil, fmt.Errorf("GetUser(%s): %w", id, err)
}
if user == nil {
return nil, fmt.Errorf("GetUser(%s): %w", id, ErrNotFound)
}
return user, nil
}
// Check wrapped errors with errors.Is and errors.As
func HandleRequest(id string) error {
user, err := GetUser(id)
if err != nil {
if errors.Is(err, ErrNotFound) {
return writeNotFound()
}
var validErr *ValidationError
if errors.As(err, &validErr) {
return writeBadRequest(validErr.Field, validErr.Message)
}
return fmt.Errorf("handling request: %w", err)
}
return writeJSON(user)
}
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.
- 4d ago First seen · 452 lines · 50 tokens per session scan A 087a737798a6
go-development is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 12d ago), licensed MIT. It adds 50 tokens to every session and 2,685 once invoked, about $0.0003 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-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-uber-fx
Golang application framework using uber-go/fx — fx.New, fx.Provide, fx.Invoke, fx.Module, fx.Lifecycle hooks, fx.Annotate (name/group/As), fx.Decorate, fx.Supply, fx.Replace, fx.WithLogger, and signal-aware Run(). Apply when using or adopting uber-go/fx, when the codebase imports go.uber.org/fx, or when wiring…