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 agentmods add commands/sgaunet/claude-plugins/gen-lintergit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/commands/sgaunet/claude-plugins/gen-linter)<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>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 | $0.00021 | $0.03112 |
| Opus 5 | $0.00010 | $0.01556 |
| Sonnet 5 | $0.00004 | $0.00622 |
| Haiku 4.5 | $0.00002 | $0.00311 |
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.
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:
-
Validate Git repository:
git rev-parse --git-dir- If fails: Exit with error "Not a git repository. Run 'git init' first."
-
Validate Go project:
test -f go.mod- If fails: Exit with error "go.mod not found. This command is for Go projects only."
-
Check existing configuration:
test -f .golangci.yml || test -f .golangci.yaml- If either exists: Store
existingConfig = trueandexistingFile = <filename> - If not exists: Store
existingConfig = false
- If either exists: Store
-
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 --versionand store for report
- If not found: Store
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.
- 5d ago First seen · 358 lines · 21 tokens per session scan A 16600b437a07
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.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
bun:migrate
Migrate existing Node.js/npm projects to Bun.