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 car12o/claude-workflows --skill go-idiomsgit clone --depth 1 https://github.com/car12o/claude-workflowsWrote 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/car12o/claude-workflows/go-idioms)<a href="https://agentmods.dev/skills/car12o/claude-workflows/go-idioms"><img src="https://agentmods.dev/badge/skills/car12o/claude-workflows/go-idioms/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/car12o/claude-workflows/go-idioms"><img src="https://agentmods.dev/badge/skills/car12o/claude-workflows/go-idioms.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.00040 | $0.00953 |
| Opus 5 | $0.00020 | $0.00477 |
| Sonnet 5 | $0.00008 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
go-idioms 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 9d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Idioms
Core Philosophy
- Simplicity over cleverness: clear, obvious code over clever abstractions
- Explicit over implicit: make intentions visible through code structure
- Composition over inheritance: build through interface composition
- Error values over exceptions: handle errors as values
Error Handling
Sentinel Errors and Wrapping
var ErrNotFound = errors.New("not found")
// Wrap with context — %w at the end
if err != nil {
return fmt.Errorf("fetching user %d: %w", userID, err)
}
if errors.Is(err, ErrNotFound) { /* handle */ }
var valErr *ValidationError
if errors.As(err, &valErr) { /* access valErr.Field */ }
Structured Errors
type AppError struct {
Code string `json:"code"`
Message string `json:"message"`
Err error `json:"-"`
}
func (e *AppError) Error() string { return e.Message }
func (e *AppError) Unwrap() error { return e.Err }
Rules
- Never ignore errors — handle or propagate explicitly
- Add context when wrapping — include relevant identifiers
- Handle once — either log or wrap+return, not both
- Panic only for programming errors, never for user input
Naming Conventions
// Packages: short, lowercase, no underscores
package user // good
package util // bad — too generic
// Avoid repetition: user.Service not user.UserService
package user
type Service struct{} // user.Service
func New() *Service // user.New()
// Interfaces: single-method = "er" suffix
type Reader interface { Read(p []byte) (int, error) }
type Repository interface {
Save(ctx context.Context, entity *Entity) error
Delete(ctx context.Context, id string) error
}
// Variables
userID // good ctx // good
uID // bad context // bad (shadows pkg)
isValid // clear bool valid // less clear
Interface Design
// Accept interfaces, return structs
func NewService(repo Repository) *Service { return &Service{repo: repo} }
func NewRepository(db *sql.DB) *PostgresRepo { return &PostgresRepo{db: db} }
// Small, composable interfaces
type Reader interface { Read(ctx context.Context, id string) (*Data, error) }
type Writer interface { Write(ctx context.Context, data *Data) error }
type ReadWriter interface { Reader; Writer }
// Compile-time compliance check
var _ Repository = (*PostgresRepo)(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.
- 9d ago First seen · 141 lines · 40 tokens per session scan A 2bd9e59caa07
go-idioms is a skill published in the GitHub repository car12o/claude-workflows (2 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 953 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
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-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…
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…
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…