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/gopherguides/gopher-ai/lint-fixgit clone --depth 1 https://github.com/gopherguides/gopher-aiWrote 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/gopherguides/gopher-ai/lint-fix)<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/lint-fix"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/lint-fix.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.00013 | $0.01686 |
| Opus 5 | $0.00006 | $0.00843 |
| Sonnet 5 | $0.00003 | $0.00337 |
| Haiku 4.5 | $0.00001 | $0.00169 |
Grade A, and why
lint-fix 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 4d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
If $ARGUMENTS is empty or not provided:
Fix all auto-fixable linting issues in the Go project.
Usage: /lint-fix [path] [options]
Examples:
/lint-fix- Fix all linting issues in project/lint-fix ./pkg/...- Fix issues in specific package/lint-fix --check- Check without fixing/lint-fix --staged- Fix only staged files
Workflow:
- Detect golangci-lint configuration
- Run linters with auto-fix enabled
- Run gofmt and goimports
- Report fixed and remaining issues
- Optionally stage fixed files
Proceed with fixing all linting issues.
If $ARGUMENTS is provided:
Fix linting issues for specified path or options.
Loop Initialization
Initialize persistent loop to ensure all fixable issues are resolved:
!if [ ! -x "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" ]; then echo "ERROR: Plugin cache stale. Run /gopher-ai-refresh (or refresh-plugins.sh) and restart Claude Code."; exit 1; else "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" "lint-fix" "COMPLETE"; fi
Configuration
Parse arguments:
- Path: Package or file to lint (default:
./...) - --check: Report issues without fixing
- --staged: Only lint staged files
- --fix-unsafe: Include unsafe fixes
Steps
1. Detect Linting Tools
# Check for golangci-lint config
ls .golangci.yml .golangci.yaml golangci.yml 2>/dev/null
# Check golangci-lint version
golangci-lint --version 2>/dev/null
2. Check Current State
# Count current issues (without fixing)
golangci-lint run --max-issues-per-linter 0 --max-same-issues 0 2>&1 | tail -20
3. Run Auto-Fix
Go formatting:
# Format all Go files
gofmt -w -s .
# Organize imports
goimports -w .
# Or use gofumpt for stricter formatting
gofumpt -w .
golangci-lint fixes:
# Run with auto-fix
golangci-lint run --fix ./...
4. Staged Files Only
When using --staged:
# Get staged Go files
STAGED=$(git diff --cached --name-only --diff-filter=ACMR | grep '\.go$')
# Format only staged files
echo "$STAGED" | xargs gofmt -w -s
echo "$STAGED" | xargs goimports -w
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.
- 4d ago First seen · 245 lines · 13 tokens per session scan A a469442745ef
lint-fix is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 1,686 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.