Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/muratmirgun/gophersnpx agentmods add skills/muratmirgun/gophers/go-lintingWrote 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/muratmirgun/gophers/go-linting)<a href="https://agentmods.dev/skills/muratmirgun/gophers/go-linting"><img src="https://agentmods.dev/badge/skills/muratmirgun/gophers/go-linting/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/muratmirgun/gophers/go-linting"><img src="https://agentmods.dev/badge/skills/muratmirgun/gophers/go-linting.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.00085 | $0.02157 |
| Opus 5 | $0.00043 | $0.01078 |
| Sonnet 5 | $0.00017 | $0.00431 |
| Haiku 4.5 | $0.00009 | $0.00216 |
Grade A, and why
go-linting 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Linting
The single most important property of a linting setup is consistency: every contributor and every CI run uses the same rules. golangci-lint is the tool; a checked-in .golangci.yml is the contract.
Core Rules
- Every Go project has a
.golangci.ymlat the repository root. It is the source of truth for which linters run. - Lint runs in CI on every PR. A green build means lint is green.
- Lint runs locally before commit. A pre-commit hook or
make lintkeeps the feedback loop fast. - Suppress with reasons.
//nolint:linter // why— never bare//nolint. - Fix the cause first. A suppression should be the last resort, not the default reaction.
- Never silence security linters (
gosec,bodyclose,sqlclosecheck) without a strong, documented reason.
Setup Procedure
- Install:
go install github.com/golangci/golangci-lint/v2/cmd/golangci-lint@latest(orbrew install golangci-lint). - Drop a baseline
.golangci.ymlat the repo root. - Run
golangci-lint run ./.... - Fix the findings in order — formatting first,
govetnext, style last. - Re-run until clean. Commit
.golangci.ymland any source fixes together. - Add the CI workflow (see references/ci-integration.md).
Minimum Linter Set
These five catch the most common issues and have the lowest noise rate. Start here:
| Linter | Catches |
|---|---|
errcheck |
Unchecked error returns |
govet |
Mistakes that compile but are wrong (printf args, shifts, etc.) |
staticcheck |
Bug-prone patterns, dead code, simplifications |
ineffassign |
Assignments whose value is never read |
revive |
Style issues (modern replacement for golint) |
Add formatting on top: gofmt / goimports (or gofumpt for stricter rules). With golangci-lint v2 these run via golangci-lint fmt.
Recommended Additional Linters
Enable these once the baseline is clean:
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 · 173 lines · 85 tokens per session scan A a55c14278be0
go-linting is a skill published in the GitHub repository muratmirgun/gophers (8 stars, last pushed 29d ago), licensed MIT. It adds 85 tokens to every session and 2,157 once invoked, about $0.0004 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
Use when writing Go services, CLIs, or libraries. Covers idiomatic error wrapping, goroutine and context discipline, interface design, table-driven tests, and the race detector.
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…
developing-genkit-go
Develop AI-powered applications using Genkit in Go. Use when the user asks to build AI features, agents, flows, or tools in Go using Genkit, or when working with Genkit Go code involving generation, prompts, streaming, tool calling, or model providers.
programming
Applies strict, modern language practice (typed errors, exhaustive match, TDD) for Python, Rust, TypeScript, and Go. Use for work on .py, .rs, .ts, or .go files.
authoring-go-sdk-tasks
Writes Airflow task logic in Go using the Airflow Go SDK. Use when the user wants to implement Airflow tasks in Go, asks about BundleProvider/RegisterDags, the bundlev1 Registry/Dag interfaces, registering Go tasks (AddTask/AddTaskWithName), dependency injection by parameter type (context.Context, sdk.TIRunContext…
deploying-go-sdk-bundles
Builds, packs, and deploys compiled Airflow Go SDK bundles so the ExecutableCoordinator can run them. Use when the user wants to compile a Go task bundle, asks about go build, go tool airflow-go-pack, the AFBNDL01 self-contained executable bundle, packing or inspecting a bundle, placing it under executablesroot…