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 n-n-code/n-n-code-skills --skill coding-guidance-gogit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWrote 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/n-n-code/n-n-code-skills/coding-guidance-go)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/coding-guidance-go"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/coding-guidance-go/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/n-n-code/n-n-code-skills/coding-guidance-go"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/coding-guidance-go.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.00068 | $0.02729 |
| Opus 5.5 | $0.00027 | $0.01092 |
| Sonnet 5.5 | $0.00014 | $0.00546 |
| Haiku 4.5 | $0.00007 | $0.00273 |
Grade A, and why
coding-guidance-go 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.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Coding Guidance
Portable Go implementation, refactoring, testing, optimization, and review guidance.
Adjacent Skills
Compose with:
- Workflow:
thinkingfor ambiguous decision framing,recursive-thinkingfor stress-testing,securityfor threat modeling - Domain overlays:
backend-guidancefor server-side code,backend-systems-guidancefor deeper backend architecture/reliability/trust boundaries,project-core-devfor repo-specific completion discovery and reporting when needed, andproject-config-and-testsfor config contracts and deterministic tests at config or path seams - Testing:
go-testing-with-testifywhen the main artifact is testify-based Go test code, test review, or Go test flake triage - TUI specialization:
coding-guidance-go-tuiwhen Bubble Tea state, Bubbles components, Lip Gloss layout, or an interactive terminal screen is the main concern
When Not to Lean on This Skill
- non-Go work
- interactive Bubble Tea or Charmbracelet terminal screens; use
coding-guidance-go-tui - pure test strategy without implementation code or concrete Go test code; use
tester-mindset - testify-specific assertion, mock, suite, or flake work; use
go-testing-with-testify - security as the primary job; use
securityand compose this skill only for Go-specific implementation details - repo-specific framework rules that should live in local docs, generated-code policy, linter config, or domain overlays
Reference Map
Load references only when the task needs that depth:
- go-concurrency-and-services.md for context, goroutine ownership, shared state, pipelines, backpressure, logging, REST/gRPC/CLI/worker boundaries, and transport error mapping
- go-testing-and-validation.md for standard Go tests, comparison choices, helpers, fuzzing, benchmarks, race checks, integration-test gating, and validation command selection
- go-performance-and-modules.md
for package/module layout,
go.mod/go.sum,go.work, vendoring, generated code, release metadata, dependency pressure, profiling, and hot-path allocation guidance - go-api-and-language-rules.md for naming, declarations, exported-contract stability, interface placement, generics, nil and collection semantics, and other detailed language rules
What ships with it
4 files 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.
- 1mo ago Changed · +1 lines 293cce4cbfc7
- 1mo ago First seen · 241 lines · 68 tokens per session scan A 8e7306a7f8bf
coding-guidance-go is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 2,729 once invoked, about $0.0003 per session on Opus 5.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
document-code
Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go…
test-go
Write, review, and improve Go test code for this project. Use whenever generating, reviewing, or modifying Go tests - including when invoked by the Tester agent, the /test prompt, or any test-related request. Covers table-driven tests, subtests, t.Parallel(), test helpers with t.Helper(), error assertions via…
golang-documentation
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices.…
golang-modernize
Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade (e.g. to Go 1.27), or a CI/tooling refresh. Not for…
golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with…
golang-cli
Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration layering, version embedding, exit codes, I/O patterns, signal handling, shell completion, argument validation, and CLI unit testing. Also triggers when code uses…