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/sirkon/gogh/agents-mdgit clone --depth 1 https://github.com/sirkon/goghWhat 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.06606 | $0.06606 |
| Opus 5 | $0.03303 | $0.03303 |
| Sonnet 5 | $0.01321 | $0.01321 |
| Haiku 4.5 | $0.00661 | $0.00661 |
Grade A, and why
gogh AGENTS.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 2d 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gogh — LLM usage context
Reference for an LLM that needs to write or modify Go code that uses the
goghlibrary to generate Go source. Module:github.com/sirkon/gogh· Go 1.26+ · Root package isgogh(all public API lives there).
What gogh is
gogh is a Go source rendering library. You build Go files programmatically by writing formatted lines through a renderer; gogh takes care of the parts that are tedious and error-prone in hand-written generators:
- collecting and emitting the
importblock, - resolving package qualifier names and alias collisions automatically,
- running
gofmt(orfancyfmt) on the result, - writing the files into the correct location inside the current Go module.
Use it when writing go generate tools, protoc plugins, schema-to-Go generators, etc. The model is "write lines that look like Go, with $placeholders for imported-package qualifiers and positional args".
Mental model (read this first)
Module[T]— one generation session, tied to the Go module on disk (discovered viago env/go mod edit). You create it once withgogh.New(...).Render()at the end flushes all files to disk. Must run inside a module directory; shells out to thegotoolchain and uses a boltDB cache for package-name lookups. That cache is self-invalidating: versioned deps are keyed by(package path, declared version)fromgo.modso a bump invalidates exactly the affected entry; replaced/workspaced/local packages are read straight from disk (cheap, always fresh, never bolt-cached); stdlib/undeclared-transitive are cached by package path. A per-module in-memory cache ensures each name is resolved at most once per Module.Package[T]— a Go package within the module. Get one from the module (Root,Current,Package,PackageName). Each package produces one or more file renderers.GoRenderer[T]— the writing surface for one Go file. You write lines into it; it owns that file's imports and rendering context.RawRenderer— likeGoRendererbut for plain-text files (no package header, no imports). Same line API.Importer/Imports— import management.Add(pkgpath).Ref("name")registers an import and binds its qualifier into the rendering context so$nameexpands to the (possibly aliased) package name.- Rendering context / scope — a hierarchical map of named values per renderer. Populated by
Ref,Let,Uniq,UniqBind, and the function helpers (ReturnssetsReturnZeroValues). Exposed in format strings as$name; positional args are$0,$1, …
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.
- 2d ago First seen · 455 lines · 6,606 tokens per session scan A 4869e4fa53d8
gogh AGENTS.md is an instructions file published in the GitHub repository sirkon/gogh (2 stars, last pushed 6d ago), licensed MIT. It adds 6,606 tokens to every session, about $0.0330 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
kubb AGENTS.md
AGENTS.md instructions for kubb-labs/kubb, covering agents.md, high-level architecture, project structure and commands, repository setup and plugin ecosystem.
figwright AGENTS.md
Instructions for awdr74100/figwright, covering agents.md, architecture, layout, tech stack and commands.
figwright CLAUDE.md
Instructions for awdr74100/figwright: Read AGENTS.md first — it's the single source of guidance for this repo: architecture, layout, tech stack, commands, conventions, release flow, and gotchas.
kessoku AGENTS.md
Instructions for mazrean/kessoku, covering repository guidelines — kessoku, project structure, common commands, build and test.
hersona CLAUDE.md
Instructions for shiro-0x/hersona, covering claude.md, update rule (keep docs in sync) and skill.md authoring rules.
lathe CLAUDE.md
Instructions for lathe-cli/lathe, covering claude.md, project intent, product positioning, source of truth and project structure.