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 Dankosik/go-service-template-rest --skill go-modern-versiongit clone --depth 1 https://github.com/Dankosik/go-service-template-restWrote 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/dankosik/go-service-template-rest/go-modern-version)<a href="https://agentmods.dev/skills/dankosik/go-service-template-rest/go-modern-version"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-modern-version/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/dankosik/go-service-template-rest/go-modern-version"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-modern-version.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.00034 | $0.00330 |
| Opus 5 | $0.00017 | $0.00165 |
| Sonnet 5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
go-modern-version 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 Modern Version
Modern Go is a version surface: the module's Go version determines which language and standard-library forms are available.
Read the affected module's go.mod. When version availability affects the
planned choice or modernization is requested, query the pinned JetBrains
inventory from the repository root against that module's Go file or go.mod:
go tool -modfile=tools/go.mod go-modern-guidelines list --file-path <path>
Reuse the inventory for the same resolved version. Read and explain only guidelines that may affect the diff. Text-only edits or edits with no version-dependent choice need no inventory. For a modernization spanning multiple files, record applicable guideline IDs and a disposition per affected file; a single local choice needs only its rationale and focused proof.
The wrong default is copying nearby legacy syntax after the target version supports a clearer form. Apply the modern form unless it changes behavior, error identity, nil or empty meaning, aliasing, ordering, performance contracts, or source ownership; those semantic owners take precedence.
Complete when the chosen forms are available at the module's version and the affected behavior is preserved with focused proof. A modernization sweep also accounts for each affected file as applied, not applicable, or blocked with an exact reason. Use the active workflow's validation plan.
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 Changed · +2 lines · +2 tokens per session 636739721269
- 11d ago First seen · 35 lines · 32 tokens per session scan A c7f7b00b437a
go-modern-version is a skill published in the GitHub repository Dankosik/go-service-template-rest (7 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 330 once invoked, about $0.0002 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-31.
Other skills, from other repositories
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
migrate-goldmark-app-v1-to-v2
Migrate your application from goldmark v1 to v2.
jwx-guide-v4
Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse/sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid the common footguns. For developers using jwx, not for developing the library itself.
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…