gen-linter

gen-linter is a skill for Claude Code from sgaunet/claude-plugins. It costs 21 tokens per session (3,116 once invoked), scanned A, original, MIT.

A generator for a golangci-lint configuration file for Go projects. A linter checks source code for likely mistakes, style problems, and other issues without running the program.

In plain words
What is it for?
Use it to create a documented .golangci.yml file with broad lint coverage that you can then customize for a Go codebase.
Why use it?
It provides a ready-made set of linting rules instead of requiring you to configure many checks and exclusions yourself.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the go-specialist plugin — 11 skills, 1 agent shipped together

Good fit Use it to create a documented .golangci.yml file with broad lint coverage that you can then customize for a Go codebase.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add sgaunet/claude-plugins
Claude Code
/plugin install go-specialist

Made for: Claude Code.

Or install go-specialist, the plugin that ships this one along with the rest of its 11 skills, 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/skills/sgaunet/claude-plugins/gen-linter/github.svg)](https://agentmods.dev/skills/sgaunet/claude-plugins/gen-linter)
Your own site
<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/gen-linter"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/gen-linter/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.

agentmods 80×15 button for gen-linter

Your own site · 80×15
<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/gen-linter"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/gen-linter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,116 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00021 $0.03116
Opus 5.5 $0.00008 $0.01246
Sonnet 5.5 $0.00004 $0.00623
Haiku 4.5 $0.00002 $0.00312

Measured 22d ago against content hash 78a6c039a44f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 22d 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/skills/gen-linter/SKILL.md · 360 lines

How it starts

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

Generate golangci-lint Configuration

Instantly create a professional .golangci.yml configuration for Go projects with comprehensive linting coverage. This skill replaces the multi-step manual setup with a single invocation.

Why This Skill 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 skill 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 · 360 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. 22d ago First seen · 360 lines · 21 tokens per session scan A 78a6c039a44f

Subscribe to this mod's changes

gen-linter is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 21 tokens to every session and 3,116 once invoked, about $0.0001 per session on Opus 5.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-09-25.

Related

Other skills, from other repositories