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 TypeFox/agent-skills --skill go-documentationgit clone --depth 1 https://github.com/TypeFox/agent-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/typefox/agent-skills/go-documentation)<a href="https://agentmods.dev/skills/typefox/agent-skills/go-documentation"><img src="https://agentmods.dev/badge/skills/typefox/agent-skills/go-documentation/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/typefox/agent-skills/go-documentation"><img src="https://agentmods.dev/badge/skills/typefox/agent-skills/go-documentation.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.00098 | $0.03753 |
| Opus 5.5 | $0.00039 | $0.01501 |
| Sonnet 5.5 | $0.00020 | $0.00751 |
| Haiku 4.5 | $0.00010 | $0.00375 |
Grade A, and why
go-documentation 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Documentation
Go treats documentation as part of the toolchain. go doc reads comments locally, pkg.go.dev publishes them, and gofmt normalizes their markup. The conventions here come from the official spec at https://go.dev/doc/comment — tools depend on them, so they are not stylistic preferences.
Coming from TypeScript
A Go doc comment is a plain // comment above a declaration — there are no tags, and almost none of the Markdown that JSDoc/TSDoc allow. These are the habits that silently produce wrong or unrendered docs; reach for the Go column instead.
| TypeScript / JSDoc habit | What Go actually does |
|---|---|
@param, @returns, @throws tags |
No tags exist. Name params and results in prose ("It returns the number of bytes written"). Types are in the signature — don't restate them. |
`inline code` backticks |
Backticks (and 'single quotes') render as curly ‘quotes’. There is no inline-code markup — use a doc link [Name] for a symbol, plain text otherwise. |
Markdown link [text](url) |
Not a link. Use a bare URL, or reference style: [text] in prose plus [text]: https://… defined at the end of the comment. |
{@link Foo} cross-reference |
Not recognized, renders as literal text. Use a doc link: [Foo]. |
Fenced ``` blocks, **bold** |
No fences, no emphasis. A code block is any line indented by one tab; **bold** renders literally. |
/** ... */ Javadoc-style block comment |
Valid Go syntax, and it does attach as the doc comment — but gofmt recognizes the leading-* pattern and deliberately leaves it untouched, so the un-stripped * on every line makes go doc/pkg.go.dev render it as a mangled code block. Use a plain // on every line instead. |
@example with a snippet |
Examples are real compiled functions (func ExampleFoo()) in _test.go, run by go test. See references/examples.md. |
@deprecated |
A paragraph beginning with the exact prefix Deprecated: . |
| Summary in any phrasing | The first sentence must start with the symbol name: Foo returns…, Package foo… (see the table below). |
| README is the docs (npmjs.com) | pkg.go.dev and go doc show the package comment, in addition to the README, above the API. |
| Indent comment text freely | Any indented line becomes a code block. Keep prose flush left. |
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.
- evals/evals.json 25 KB
- evals/files/jsdoc-comments/go.mod 63 B
- evals/files/jsdoc-comments/tokenbucket.go 2.2 KB
- evals/files/package-overview/go.mod 59 B
- evals/files/package-overview/README.md 1.5 KB
- evals/files/package-overview/store.go 1.1 KB
- evals/files/testable-examples/go.mod 56 B
- evals/files/testable-examples/slug.go 1.5 KB
- references/comment-syntax.md 18 KB
- references/examples.md 7.8 KB
- references/pkgsite-preview.md 8.3 KB
- references/publishing.md 9.8 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.
- 1mo ago First seen · 256 lines · 98 tokens per session scan A 1f90eada55b4
go-documentation is a skill published in the GitHub repository TypeFox/agent-skills (5 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 3,753 once invoked, about $0.0004 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
loom-golang
Go language expertise for idiomatic, production-quality code. Not for: an LLM's context window or a stage's context budget.
authoring-go-sdk-tasks
Writes Airflow task logic in Go using the Airflow Go SDK. Use when the user wants to implement Airflow tasks in Go, asks about BundleProvider/RegisterDags, the bundlev1 Registry/Dag interfaces, registering Go tasks (AddTask/AddTaskWithName), dependency injection by parameter type (context.Context, sdk.TIRunContext…
deploying-go-sdk-bundles
Builds, packs, and deploys compiled Airflow Go SDK bundles so the ExecutableCoordinator can run them. Use when the user wants to compile a Go task bundle, asks about go build, go tool airflow-go-pack, the AFBNDL01 self-contained executable bundle, packing or inspecting a bundle, placing it under executablesroot…
loom-typescript
TypeScript language expertise for type-safe, production-quality code.
loom-python
Python language expertise for idiomatic, production-quality code.
loom-rust
Rust language expertise for idiomatic, production-quality code.