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 atstaeff/ai-agents --skill golang-patternsgit clone --depth 1 https://github.com/atstaeff/ai-agentsWrote 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/atstaeff/ai-agents/golang-patterns)<a href="https://agentmods.dev/skills/atstaeff/ai-agents/golang-patterns"><img src="https://agentmods.dev/badge/skills/atstaeff/ai-agents/golang-patterns/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/atstaeff/ai-agents/golang-patterns"><img src="https://agentmods.dev/badge/skills/atstaeff/ai-agents/golang-patterns.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.00019 | $0.03154 |
| Opus 5 | $0.00010 | $0.01577 |
| Sonnet 5 | $0.00004 | $0.00631 |
| Haiku 4.5 | $0.00002 | $0.00315 |
Grade A, and why
golang-patterns 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 8d 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 — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Golang Patterns Skill
Instructions for AI
Apply idiomatic Go patterns, modern best practices, and production-grade code standards. Use this skill when writing, reviewing, or refactoring Go code. Follow Go's philosophy: simplicity, clarity, composition.
Reference: Effective Go, Go Code Review Comments, Uber Go Style Guide.
Core Patterns
1. Repository Pattern with Interfaces
Abstraction over data access, enabling testability and swappable backends.
type OrderRepository interface {
Create(ctx context.Context, order *Order) error
GetByID(ctx context.Context, id uuid.UUID) (*Order, error)
List(ctx context.Context, filter OrderFilter) ([]Order, error)
Update(ctx context.Context, order *Order) error
Delete(ctx context.Context, id uuid.UUID) error
}
// PostgreSQL implementation
type postgresOrderRepo struct {
db *sql.DB
}
func NewPostgresOrderRepo(db *sql.DB) OrderRepository {
return &postgresOrderRepo{db: db}
}
func (r *postgresOrderRepo) GetByID(ctx context.Context, id uuid.UUID) (*Order, error) {
var o Order
err := r.db.QueryRowContext(ctx,
`SELECT id, customer_id, total, status, created_at
FROM orders WHERE id = $1`, id,
).Scan(&o.ID, &o.CustomerID, &o.Total, &o.Status, &o.CreatedAt)
if errors.Is(err, sql.ErrNoRows) {
return nil, fmt.Errorf("order %s: %w", id, ErrNotFound)
}
if err != nil {
return nil, fmt.Errorf("querying order %s: %w", id, err)
}
return &o, nil
}
2. Service Layer with Dependency Injection
Business logic encapsulated in services with injected dependencies.
type OrderService struct {
repo OrderRepository
events EventPublisher
logger *slog.Logger
}
func NewOrderService(repo OrderRepository, events EventPublisher, logger *slog.Logger) *OrderService {
return &OrderService{repo: repo, events: events, logger: logger}
}
func (s *OrderService) PlaceOrder(ctx context.Context, cmd PlaceOrderCommand) (*Order, error) {
order, err := NewOrder(cmd.CustomerID, cmd.Items)
if err != nil {
return nil, fmt.Errorf("creating order: %w", err)
}
if err := s.repo.Create(ctx, order); err != nil {
return nil, fmt.Errorf("saving order: %w", err)
}
if err := s.events.Publish(ctx, "orders.placed", OrderPlacedEvent{
OrderID: order.ID,
CustomerID: order.CustomerID,
Total: order.Total,
}); err != nil {
s.logger.WarnContext(ctx, "event publish failed", slog.String("error", err.Error()))
}
return order, nil
}
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.
- 8d ago First seen · 438 lines · 19 tokens per session scan A ffa558919948
golang-patterns is a skill published in the GitHub repository atstaeff/ai-agents (2 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 3,154 once invoked, about $0.0001 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
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…
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…
golang-samber-oops
Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports…
ax-go-agent-optimize
Use when writing Go code with github.com/ax-llm/ax/packages/go for agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA.
gmeasure
Benchmark and measure Go code with gmeasure — an Experiment groups named Measurements, recorded via RecordValue/RecordDuration/MeasureDuration or repeated Sample/SampleValue/SampleDuration with SamplingConfig, timed inline with a Stopwatch, summarized through GetStats/Stats (StatMin/Max/Mean/Median/StdDev…