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 cboone/agent-harness-plugins --skill write-go-codegit clone --depth 1 https://github.com/cboone/agent-harness-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/cboone/agent-harness-plugins/write-go-code)<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/write-go-code"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/write-go-code/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/cboone/agent-harness-plugins/write-go-code"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/write-go-code.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.00046 | $0.00525 |
| Opus 5.5 | $0.00018 | $0.00210 |
| Sonnet 5.5 | $0.00009 | $0.00105 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
write-go-code 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 9d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Go Code
Core Principles
- Clarity over cleverness - Code should be obvious to readers
- Simplicity - Accomplish goals in the most straightforward way
- Consistency - Match surrounding code and project conventions
- Minimal indentation - Handle errors early, keep happy path unindented
Workflow
- Run automated checks (
make lint,make fmtorgofmt,goimports) - Review against essential checklist:
references/essential/checklist.md - For specific questions, consult:
references/comprehensive/{topic}.md - When creating or editing Cobra root commands, consult:
references/comprehensive/cobra.md
Reference Navigation
Quick reviews (default):
references/essential/checklist.md- Condensed, actionable rules
Deep dives by topic:
references/comprehensive/naming.md- Package names, identifiers, receiversreferences/comprehensive/errors.md- Error handling, panic/recoverreferences/comprehensive/concurrency.md- Goroutines, channels, contextreferences/comprehensive/testing.md- Test quality and patternsreferences/comprehensive/code-organization.md- Imports, packages, structurereferences/comprehensive/data-types.md- new vs make, slices, mapsreferences/comprehensive/functions.md- Multiple returns, deferreferences/comprehensive/interfaces.md- Embedding, type assertionsreferences/comprehensive/makefile-conventions.md- Required CI targets, fmt vs formatreferences/comprehensive/cobra.md- Cobra root command usage templates
Pull Request Review
When reviewing a pull request, apply ./references/review-checklist.md: the rules of this guide that a reviewer can check in a diff, ranked as Important, Nits and Do not flag. The same checklist is installed into repositories for automated reviewers, so update it whenever a rule here changes.
Sources
What ships with it
12 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.
- references/comprehensive/cobra.md 5.4 KB
- references/comprehensive/code-organization.md 3.6 KB
- references/comprehensive/concurrency.md 3.5 KB
- references/comprehensive/data-types.md 3.8 KB
- references/comprehensive/errors.md 3.2 KB
- references/comprehensive/functions.md 4.2 KB
- references/comprehensive/interfaces.md 4.8 KB
- references/comprehensive/makefile-conventions.md 1.7 KB
- references/comprehensive/naming.md 3.1 KB
- references/comprehensive/testing.md 3.2 KB
- references/essential/checklist.md 4.4 KB
- references/review-checklist.md 4.3 KB
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.
- 9d ago Changed · +1 lines · +11 tokens per session 136c0c6e81fb
- 25d ago Changed · +4 lines d116396f873a
- 26d ago Changed · -3 lines · -51 tokens per session 08cc1b3cd6b9
- 1mo ago First seen · 51 lines · 86 tokens per session scan A 2fb4727f1e8e
write-go-code is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 525 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
google-go-style
Use when writing, reviewing, or refactoring Go code; when handling errors (fmt.Errorf, %w, sentinel, errors.Is, errors.As); when deciding between panic, error return, and log.Fatal; when writing tests (table-driven, t.Helper, t.Fatal vs t.Error, goroutines); when designing API surface (option struct, variadic options…
golang-refactoring
Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, gofmt -r, gopatch), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code…
go-concurrency-safety
L1 supplement - audits Go-specific concurrency hazards in node client code: map iteration non-determinism, goroutine leaks, mutex ordering, panic boundaries, context cancellation.
go-architecture-review
Good architecture makes the next change easy. Bad architecture makes every change scary.
context-lifecycle
Review goroutines, timers, callbacks, actor handoffs, and async cleanup for context lifetime bugs. Use when code starts work that may outlive the caller, especially from RPC handlers, wallet startup, daemon startup, actors, or notification registrations.
go-design
Structure and restructure Go code the Go way: dependency direction between packages, consumer-defined interfaces, composition instead of inheritance, smell-driven refactoring in small safe steps, and changing untested code with characterization tests and seams. Use when placing code in a RonyKit feature module…