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 skills add wangke19/gemini-ai-helpers --skill lintgit 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/skills/wangke19/gemini-ai-helpers/lint)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/lint"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/lint/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/skills/wangke19/gemini-ai-helpers/lint"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/lint.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.00021 | $0.01029 |
| Opus 5 | $0.00010 | $0.00515 |
| Sonnet 5 | $0.00004 | $0.00206 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade C, and why
Go Lint scanned grade C with 2 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 7d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- macOS/Linux: `curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(go env GOPATH)/bin` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- macOS/Linux: `curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(go env GOPATH)/bin` How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Lint
This skill detects the best way to run golangci-lint in the current Go repository and executes it, reporting results in a structured summary.
When to Use This Skill
Use this skill when:
- The user asks to run the linter, check for lint issues, or verify code quality in a Go project
- Another command needs to run golangci-lint as a prerequisite step (e.g.,
golang:lint-fix) - The agent decides linting is needed before committing Go code changes
Prerequisites
- A Go repository (contains
go.mod) golangci-lintinstalled, or the ability to install it (see Step 6 below)
Implementation Steps
Step 1: Detect the Lint Command
Try the following approaches in order. Proceed to Step 2 once any approach succeeds:
-
Check project documentation first - Read
AGENTS.mdorCLAUDE.mdin the repository root (if they exist) and look for linting instructions (e.g.,make lint,make verify, specific golangci-lint commands, or other linter commands). If found, use those instructions. -
Check for lint scripts - Many repositories (especially OpenShift projects) have scripts that run golangci-lint in a containerized way with repo-specific configuration. Check for these patterns and run if found:
hack/go-lint.shhack/lint.shhack/verify-golangci-lint.shhack/verify-lint.shscripts/go-lint.shscripts/lint.sh- Or any other
*lint*.shscript inhack/orscripts/directories
-
Check the Makefile - Look for a make target like
make lintormake verify-lint, and run it. -
Run golangci-lint directly - Try:
golangci-lint run -
Try GOPATH binary - If golangci-lint was not found on PATH, try:
$(go env GOPATH)/bin/golangci-lint run
-
Install golangci-lint - If not installed, inform the user how to install it:
- macOS/Linux:
curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(go env GOPATH)/bin - Or using go install:
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest - Then retry from step 4.
- macOS/Linux:
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.
- 7d ago First seen · 94 lines · 21 tokens per session scan C a63355472ae6
Go Lint is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,029 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…
sentry-go-sdk
Full Sentry SDK setup for Go. Use when asked to "add Sentry to Go", "install sentry-go", "setup Sentry in Go", or configure error monitoring, tracing, logging, metrics, or crons for Go applications. Supports net/http, Gin, Echo, Fiber, FastHTTP, Iris, Negroni, and gRPC.
kessoku-di
Kessoku compile-time DI with parallel initialization for Go. Use when writing or debugging kessoku providers/injectors, enabling async dependencies, migrating from google/wire, or fixing go:generate/codegen issues in Go services.
debugging-guide
Use when debugging Go errors, test failures, or unexpected behavior — step-by-step diagnosis approach.
go-concurrency-patterns
Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.
otel-go-reviewer
Review pull requests, diffs, patches, or design proposals for the open-telemetry/opentelemetry-go repository with a senior maintainer mindset. Use when changes in opentelemetry-go may affect OpenTelemetry specification compliance, repository contribution rules, changelog requirements, module versioning boundaries, API…