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/sgaunet/claude-plugins/go-toolnpx skills add sgaunet/claude-plugins --skill go-toolgit 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/skills/sgaunet/claude-plugins/go-tool)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/go-tool"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/go-tool.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.00052 | $0.01340 |
| Opus 5 | $0.00026 | $0.00670 |
| Sonnet 5 | $0.00010 | $0.00268 |
| Haiku 4.5 | $0.00005 | $0.00134 |
Grade A, and why
go-tool 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Tool Dependency Management
Manage Go development tool dependencies using the tool directive introduced in Go 1.24. This ensures reproducible builds by tracking tool versions in go.mod — eliminating the old tools.go workaround and version drift across developers and CI.
For detailed per-tool information, see the reference catalog.
When to Use
- A Go project needs external code generation or build tools
- Indicator files suggest a tool should be added (
.templ,.proto,sqlc.yml, etc.) - The user explicitly requests adding a Go tool dependency
- Auditing existing tool dependencies for consistency or cleanup
Prerequisites
Before proceeding, verify:
- go.mod exists: Check for
go.modin the project root. Abort if missing. - Go version ≥ 1.24: Read the
godirective ingo.mod. If the version is below 1.24, inform the user: "The Go tool directive requires Go 1.24+. Update thegodirective in go.mod to 1.24 or later."
Workflow: Detect Recommended Tools
Scan the project for indicator files and compare against existing tool declarations in go.mod.
Step 1: Read Existing Tools
Parse go.mod for the tool block to identify already-tracked tools.
Step 2: Scan for Indicator Files
Use Glob to detect files that suggest specific tools:
| Indicator | Tool | Module Path |
|---|---|---|
sqlc.yml / sqlc.yaml / sqlc.json |
sqlc | github.com/sqlc-dev/sqlc/cmd/sqlc |
**/*.templ |
templ | github.com/a-h/templ/cmd/templ |
swagger.yaml / swagger.json |
swag | github.com/swaggo/swag/cmd/swag |
For stringer and enumer, detection requires context: const blocks with iota patterns. These are best suggested when the user is working with enum-like types. Prefer enumer over stringer when the type also needs JSON, SQL, or text marshalling; stringer only generates String().
Step 3: Report Findings
Present a table comparing detected recommendations against existing tools:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 156 lines · 52 tokens per session scan A 5d53ca5d35ee
go-tool is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 1,340 once invoked, about $0.0003 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 skills, from other repositories
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.