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 skills/rootwarp/claude-code-plugins-monorepo/go-lintnpx skills add rootwarp/claude-code-plugins-monorepo --skill go-lintgit clone --depth 1 https://github.com/rootwarp/claude-code-plugins-monorepoWrote 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/rootwarp/claude-code-plugins-monorepo/go-lint)<a href="https://agentmods.dev/skills/rootwarp/claude-code-plugins-monorepo/go-lint"><img src="https://agentmods.dev/badge/skills/rootwarp/claude-code-plugins-monorepo/go-lint.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.00000 | $0.00081 |
| Opus 5 | $0.00000 | $0.00041 |
| Sonnet 5 | $0.00000 | $0.00016 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
go-lint 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.
What it actually says
/go-lint
Run linters on the Go project.
Instructions
Run golangci-lint if available, otherwise use go vet:
if command -v golangci-lint &> /dev/null; then
golangci-lint run ./...
else
go vet ./...
fi
Analyze any lint warnings or errors and suggest fixes.
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 · 18 lines · 0 tokens per session scan A 853edb7750fc
go-lint is a skill published in the GitHub repository rootwarp/claude-code-plugins-monorepo (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 81 tokens. 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-31.
Other skills, from other repositories
go-effective
Validate Go code against Effective Go and idiomatic conventions.
go-proverbs
Validate Go code changes against Go Proverbs.
go-idioms
写 Go 时使用。地道 Go：错误处理、并发、接口的正确姿势。.
cmd_go_build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
cmd_go_review
Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.
cmd_go_test
Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.