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 medy-gribkov/arcana --skill go-linter-configurationgit clone --depth 1 https://github.com/medy-gribkov/arcanaWrote 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/medy-gribkov/arcana/go-linter-configuration)<a href="https://agentmods.dev/skills/medy-gribkov/arcana/go-linter-configuration"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/go-linter-configuration/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/medy-gribkov/arcana/go-linter-configuration"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/go-linter-configuration.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.02413 |
| Opus 5 | $0.00020 | $0.01207 |
| Sonnet 5 | $0.00008 | $0.00483 |
| Haiku 4.5 | $0.00004 | $0.00241 |
Grade A, and why
go-linter-configuration 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 11d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Installation
# BAD: install via go get (deprecated)
go get -u github.com/golangci/golangci-lint/cmd/golangci-lint
# GOOD: install latest with go install
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
# Or install via package manager
# macOS: brew install golangci-lint
# Windows: choco install golangci-lint
# Linux: snap install golangci-lint --classic
Verify installation:
golangci-lint --version
# golangci-lint has version 1.61.0 built with go1.23.4
Complete Configuration Examples
Minimal (CI with Import Issues)
When CI fails with "undefined: package" errors despite local builds working:
# .golangci.yml
run:
timeout: 5m
tests: false # Skip test files (often have complex imports)
build-tags: [] # No build tags
skip-dirs: # Skip generated/vendor code
- vendor
- third_party
- testdata
linters:
disable-all: true # Start from scratch
enable:
- gofmt # Only check formatting (no type-checking)
- goimports # Check imports
linters-settings:
gofmt:
simplify: true # Use gofmt -s
issues:
exclude-use-default: false
max-issues-per-linter: 0 # Report all issues
max-same-issues: 0 # No deduplication
output:
formats:
- format: colored-line-number
sort-results: true
Standard (Local Development)
# .golangci.yml
run:
timeout: 5m
tests: true
build-tags:
- integration
skip-dirs:
- vendor
- third_party
modules-download-mode: readonly # Don't modify go.mod
linters:
enable:
- gofmt # Format checking
- goimports # Import organization
- govet # Go vet built-in
- errcheck # Unchecked errors
- staticcheck # Static analysis
- unused # Unused code
- gosimple # Simplifications
- ineffassign # Ineffective assignments
- typecheck # Type errors
- misspell # Spelling
- gocyclo # Cyclomatic complexity
- dupl # Code duplication
- gosec # Security issues
linters-settings:
govet:
enable-all: true
disable:
- shadow # Too noisy for most projects
errcheck:
check-type-assertions: true
check-blank: true
staticcheck:
checks: ["all"]
gocyclo:
min-complexity: 15 # Flag functions with complexity > 15
dupl:
threshold: 100 # Tokens threshold for duplication
gosec:
excludes:
- G104 # Unhandled errors (covered by errcheck)
misspell:
locale: US
issues:
exclude-rules:
# Exclude linters for test files
- path: _test\.go
linters:
- gocyclo
- dupl
# Exclude known false positives
- text: "weak cryptographic primitive"
linters:
- gosec
path: test/
max-issues-per-linter: 50
max-same-issues: 3
output:
formats:
- format: colored-line-number
print-issued-lines: true
print-linter-name: true
sort-results: true
What ships with it
2 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.
- 11d ago First seen · 410 lines · 40 tokens per session scan A b80597fedcbc
go-linter-configuration is a skill published in the GitHub repository medy-gribkov/arcana (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,413 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
golang-safety
Defensive Golang coding to prevent panics, silent data corruption, and subtle runtime bugs. Use whenever writing or reviewing Go code that involves nil-prone types (pointers, interfaces, maps, slices, channels), numeric conversions, resource lifecycle (defer in loops), or defensive copying. Also triggers on questions…
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-troubleshooting
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production…
golang-error-handling
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log…
golang-lint
Provides linting best practices and golangci-lint configuration for Go projects. Covers running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and managing linter settings. Use this skill whenever the user runs linters, configures golangci-lint, asks about…
python-memory-safe-scripts
Memory-safe Python script patterns for long-running processes under systemd MemoryMax constraints. Covers allocator purge (mimalloc/glibc malloctrim), HTTP response lifecycle, DataFrame cleanup, thread-local connection reuse, and periodic GC cadence. Battle-tested through 5 OOM optimization cycles on production GPU…