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/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/plugins/gopherguides/gopher-ai/go-dev)<a href="https://agentmods.dev/plugins/gopherguides/gopher-ai/go-dev"><img src="https://agentmods.dev/badge/plugins/gopherguides/gopher-ai/go-dev/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/plugins/gopherguides/gopher-ai/go-dev"><img src="https://agentmods.dev/badge/plugins/gopherguides/gopher-ai/go-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
go-dev 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 1mo 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
{
"name": "go-dev",
"description": "Go-specific development tools with idiomatic best practices",
"version": "1.11.3",
"author": {
"name": "Gopher Guides",
"email": "[email protected]"
},
"homepage": "https://gopherguides.com",
"repository": "https://github.com/gopherguides/gopher-ai",
"license": "MIT",
"keywords": [
"go",
"testing",
"lint",
"explain",
"best-practices"
]
}
What it installs
The manifest is a name and a version. 11 skills, 10 commands travel with it, and installing the plugin installs all of them — 644 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill go-profiling-optimization A 101 tokens
- Skill go A 83 tokens
- Skill validate-skills A 49 tokens
- Skill bench A 33 tokens
- Skill explain A 39 tokens
- Skill lint-fix A 38 tokens
- Skill refactor-clean A 39 tokens
- Skill test-gen A 41 tokens
- Skill verify A 35 tokens
- Skill build-fix A 37 tokens
- Skill profile A 35 tokens
- Command build-fix A 13 tokens
- Command refactor-clean A 14 tokens
- Command bench A 10 tokens
- Command explain A 9 tokens
- Command lint-fix A 13 tokens
- Command profile A 14 tokens
- Command test-gen A 8 tokens
- Command verify A 18 tokens
- Command validate-skills A 10 tokens
- Command cancel-loop A 5 tokens
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.
- 1mo ago Changed 11afc4e9b653
- 1mo ago Changed f63697e4080b
- 1mo ago Changed bed1150ae71b
- 1mo ago Changed ac79c58ccc35
- 1mo ago Changed acd068c14a71
- 1mo ago First seen · 20 lines scan A db9efd6b8262
go-dev is a plugin published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
jwx-dev-v4
Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse and sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid common footguns.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
golang-skills
20 modular skills for idiomatic Go — each under 225 lines, backed by 48 reference files, 8 automation scripts (all with --json, --limit, --force), and 4 asset templates. Covers error handling, naming, testing, concurrency, interfaces, generics, documentation, logging, performance, and more. Activates automatically…
claude-go
Go language support: goimports auto-formatting on file edits, Go coding conventions.
go-standards
Stdlib-grounded Go engineering standards for implementation, review, refactoring, and testing.
aio-golang-mastery
Write and lint idiomatic Go end-to-end — a 7-tool lint chain (build, vet, golangci-lint, govulncheck, nilaway, deadcode, race) plus reference-grade patterns for concurrency, errors, generics, gRPC, naming/style enforcement (revive 21-rule set, golangci-lint v2 production config), and production hardening.