gen-linter

gen-linter is a command for coding agents from sgaunet/claude-plugins. It costs 21 tokens per session (3,112 once invoked), scanned A, original, MIT.

A command that creates a .golangci.yml file for golangci-lint, a tool that checks Go code for many common problems and style issues.

In plain words
What is it for?
Use it to set up comprehensive Go linting for a project by generating the linter configuration file.
Why use it?
It avoids manually choosing and configuring a large set of linters while providing a starting configuration that can be customized.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the go-specialist plugin — 4 skills, 7 commands, 1 agent shipped together

Install

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.

agentmods
npx agentmods add commands/sgaunet/claude-plugins/gen-linter
Clone the repo
git clone --depth 1 https://github.com/sgaunet/claude-plugins

Or install go-specialist, the plugin that ships this one along with the rest of its 4 skills, 7 commands, 1 agent.

Wrote 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.

agentmods badge for gen-linter

README.md
[![agentmods](https://agentmods.dev/badge/commands/sgaunet/claude-plugins/gen-linter.svg)](https://agentmods.dev/commands/sgaunet/claude-plugins/gen-linter)
Your own site
<a href="https://agentmods.dev/commands/sgaunet/claude-plugins/gen-linter"><img src="https://agentmods.dev/badge/commands/sgaunet/claude-plugins/gen-linter.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,112 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.03112
Opus 5 $0.00010 $0.01556
Sonnet 5 $0.00004 $0.00622
Haiku 4.5 $0.00002 $0.00311

Measured 5d ago against content hash 16600b437a07, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gen-linter 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 5d 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.

plugins/go-specialist/commands/gen-linter.md · 358 lines

How it starts

The opening of the file, as written. The whole thing — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate golangci-lint Configuration Command

Instantly create a professional .golangci.yml configuration for Go projects with comprehensive linting coverage. This command converts the multi-step linter skill into a one-command solution.

Why This Command Exists

Problem: Setting up golangci-lint requires manually creating YAML configuration, understanding 90+ linter options, and balancing strict quality checks with pragmatic development - a 15-30 minute process prone to over-configuration.

Solution: One-command generation that:

  • Creates battle-tested .golangci.yml (224 lines)
  • Enables all linters by default with sensible exclusions
  • Balances code quality with development velocity
  • Works out-of-the-box for most Go projects
  • Includes inline documentation for customization

Content Generation Rules

CRITICAL: When generating any content (configuration files, commit messages, or any other output):

  • NEVER add Claude Code attribution or co-authorship
  • NEVER include phrases like "Generated by Claude", "Created with Claude Code", or similar
  • NEVER add "Co-Authored-By: Claude" in commit messages or documentation
  • All generated content should appear as if written by a human developer
  • Focus on technical accuracy and providing working templates

Process (6 Phases)

Phase 1: Prerequisites Validation

Critical checks before proceeding:

  1. Validate Git repository:

    git rev-parse --git-dir
    
    • If fails: Exit with error "Not a git repository. Run 'git init' first."
  2. Validate Go project:

    test -f go.mod
    
    • If fails: Exit with error "go.mod not found. This command is for Go projects only."
  3. Check existing configuration:

    test -f .golangci.yml || test -f .golangci.yaml
    
    • If either exists: Store existingConfig = true and existingFile = <filename>
    • If not exists: Store existingConfig = false
  4. Check for golangci-lint binary (non-blocking):

    command -v golangci-lint
    
    • If not found: Store linterNotInstalled = true (will show warning later)
    • If found: Check version with golangci-lint --version and store for report

Read the full file on GitHub · 358 lines

Changes

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.

  1. 5d ago First seen · 358 lines · 21 tokens per session scan A 16600b437a07

Subscribe to this mod's changes

gen-linter is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 3,112 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-30.