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.
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/lint-fix)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/lint-fix"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/lint-fix/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/commands/wangke19/gemini-ai-helpers/lint-fix"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/lint-fix.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.00012 | $0.00989 |
| Opus 5 | $0.00006 | $0.00495 |
| Sonnet 5 | $0.00002 | $0.00198 |
| Haiku 4.5 | $0.00001 | $0.00099 |
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 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
golang:lint-fix
Synopsis
/golang:lint-fix
/golang:lint-fix [<linter-flags>]
Description
This command runs golangci-lint and systematically fixes all reported issues in the codebase. It creates a todo list to track progress and fixes issues by category until all linter checks pass.
This command handles common linter categories including goconst, gocyclo, prealloc, revive, staticcheck, and unparam with appropriate fix strategies for each.
Implementation
Follow this process:
-
Run the "Go Lint" skill to identify all issues, extract the
golangci-lintexact call from the skill and remember it. Pass through any additional flags the user provided. -
With the exact
golangci-lintcommand, run with--fixappended, to automatically fix any auto-fixable issues.- Note: If the "Go Lint" skill used
hack/go-lint.sh(a containerized script), the--fixflag cannot be passed to it. In this case, rungolangci-lint run --fixdirectly (using the same config file if one exists in the repo, e.g.,--config=.golangci.yaml).
- Note: If the "Go Lint" skill used
-
For the rest of the issues, create a todo list to track fixing each category of issues
-
Fix all issues systematically using these example strategies:
- goconst: Add constants for repeated strings (3+ occurrences)
- gocyclo: Add
//nolint:gocyclocomments for complex test functions with justification - prealloc: Pre-allocate slices when capacity is known using
make([]T, 0, capacity) - revive: Fix comment spacing issues (add space after
//) - staticcheck: Fix deprecated code, remove redundant checks, fix naming conventions (ErrFoo for errors)
- unparam: Remove unused parameters or always-nil error returns
-
Re-run exact
golangci-lintcommand again after each category to verify fixes -
Continue until all issues are resolved
Important Guidelines
- For test files with high cyclomatic complexity, add
//nolint:gocyclowith reason "Table-driven test with inherent complexity" - For generated files, add
//nolintcomments rather than modifying the code - For Ginkgo/Gomega dot imports, add
//nolint:staticcheck,revivewith reason "Ginkgo/Gomega DSL convention" - When creating constants, check if one already exists in the package before adding a new one
- Use existing constants from other packages when appropriate
- For functions that always return nil error, remove the error return and update all callers
- For unused parameters, either remove them or add
//nolint:unparamif they're needed for interface compatibility
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 · 107 lines · 12 tokens per session scan A f69406cec397
lint-fix is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 989 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-09-03.
Other commands, from other repositories
go-build
A command for diagnosing and fixing Go build errors, vet warnings, and linter problems in small, incremental changes. Go is a programming language, and these tools check whether Go code builds and follows common rules.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
go-build
Fix Go build and vet errors.
go-build
Fix Go build and vet errors.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.