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 agentmods add instructions/hiromaily/docs-ssot/gogit clone --depth 1 https://github.com/hiromaily/docs-ssotWrote 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/instructions/hiromaily/docs-ssot/go)<a href="https://agentmods.dev/instructions/hiromaily/docs-ssot/go"><img src="https://agentmods.dev/badge/instructions/hiromaily/docs-ssot/go.svg" alt="Measured on agentmods" 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 | $0.01213 | $0.01213 |
| Opus 5 | $0.00607 | $0.00607 |
| Sonnet 5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
docs-ssot go.instructions.md 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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go File Rules
Go version
This project uses Go 1.26. Prefer modern language and standard library features:
for rangeover integers (for i := range n) — available since Go 1.22slicesandmapspackages from the standard libraryanyinstead ofinterface{}t.Context()in tests instead ofcontext.Background()errors.Newfor static error strings;fmt.Errorf("...: %w", err)for error wrappingnew(expr)for pointer literals — available since Go 1.26
Pointer literals
Go 1.26 allows passing expressions directly to new, eliminating the need for a temporary variable or helper functions like ToPtr():
// Before Go 1.26 — create a temp variable first
n := int64(300)
ptr := &n
// Also before — helper function workaround
func ToPtr[T any](v T) *T { return &v }
ptr := ToPtr(int64(300))
// Go 1.26+ — pass the expression directly
ptr := new(int64(300))
Rules:
- Do not define or use
ToPtr,Ptr, or similar pointer-helper functions. - Do not create a temporary variable solely to take its address.
- Use
new(expr)for all pointer literals to optional/nullable fields.
Toolchain setup
All Go commands run from mcp-server/. The module lives at github.com/hiromaily/claude-forge/mcp-server.
To set up the dev environment (installs lefthook hooks and pins golangci-lint as a tool in go.mod):
cd mcp-server && make install
golangci-lint is pinned as a Go tool dependency (go get -tool — available since Go 1.24). Run it via go tool golangci-lint, not a globally installed binary. The version is locked in go.mod under the tool directive.
Running tests
cd mcp-server && go test ./...
Git hooks (lefthook)
Lefthook runs automatically on git operations. Both hooks only trigger when **/*.go files are staged/pushed, and both run from mcp-server/.
| Hook | Command | Behaviour |
|---|---|---|
pre-commit |
make go-fmt |
Formats staged .go files and re-stages the fixes (stage_fixed: true) |
pre-push |
make go-lint |
Lints and auto-fixes .go files before push |
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.
- 4d ago First seen · 104 lines · 1,213 tokens per session scan A 4a3fdf0818f1
docs-ssot go.instructions.md is an instructions file published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,213 tokens to every session, about $0.0061 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 instructions, from other repositories
ollama CLAUDE.md
Claude Code instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
gorest AGENTS.md
AGENTS.md instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.
chatgpt-cli CLAUDE.md
Claude Code instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
kessoku AGENTS.md
AGENTS.md instructions for mazrean/kessoku, covering repository guidelines — kessoku, project structure, common commands, build and test.
ketch CLAUDE.md
Claude Code instructions for 1broseidon/ketch, covering ketch, architecture, build & test, output format and output flags (all commands).