What is gosymdb CLAUDE.md?

Project instructions for gosymdb, a Go code index that understands resolved symbols and their relationships. Unlike text search, it can identify which functions, types, and interfaces are actually connected in the compiled code model.

Use it to navigate the gosymdb Go repository, find callers and implementations, assess the impact of changing a symbol, and resolve fully qualified names.

It helps answer Go navigation questions that ordinary search can get wrong, such as who calls a function or what implements an interface. The instructions also explain how to initialize and refresh the project index.

How walkindude/gosymdb configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to walkindude/gosymdb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/walkindude/gosymdb/master/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/walkindude/gosymdb

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/walkindude/gosymdb/claude-md/github.svg)](https://agentmods.dev/instructions/walkindude/gosymdb/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/walkindude/gosymdb/claude-md"><img src="https://agentmods.dev/badge/instructions/walkindude/gosymdb/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/walkindude/gosymdb/claude-md"><img src="https://agentmods.dev/badge/instructions/walkindude/gosymdb/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,400 This file is loaded in full into every session.

When invoked 1,400 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01400	$0.01400
Opus 5.5	$0.00560	$0.00560
Sonnet 5.5	$0.00280	$0.00280
Haiku 4.5	$0.00140	$0.00140

Measured 2mo ago against content hash e3205823728c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gosymdb CLAUDE.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 2mo 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.

CLAUDE.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Working on gosymdb

This is the gosymdb repo. The binary built here is the typed Go symbol index, and running it against this codebase is the canonical way to navigate, since the schema and command surface match the source you're editing.

gosymdb resolves symbols via Go's go/packages and go/types (the loader and typechecker the compiler uses), not by string matching. For Go-semantic questions ("who calls X", "what implements Y", "what breaks if I change Z") it returns concrete answers with file paths, line numbers, and fully-qualified names. Grep finds string occurrences; gosymdb finds resolved symbols. The two answer different questions, and either is the right tool depending on what's being asked.

Session-start bootstrap

gosymdb agent-context

agent-context always emits JSON with the full command reference plus an env block (cwd, db path, stale_packages, git state). Reading it once at the top of a session removes the need for --help calls later.

If env.db is empty, no database has been built. The path that fixes this:

gosymdb index --root . --db gosymdb.sqlite
gosymdb agent-context   # env.db now populated

After that, subsequent commands auto-discover the database from cwd or its ancestors; an explicit --db flag is only needed for non-default paths.

Task	Command
Where is this symbol defined?	`gosymdb def FuncName --json`
What calls this function?	`gosymdb callers --symbol <fqname> --json`
What does this function call?	`gosymdb callees --symbol <fqname> --json`
What's in this file?	`gosymdb find --file <path> --json`
What's in this package?	`gosymdb find --pkg <pkg> --json`
List all symbols in the DB	`gosymdb find --json` (up to `--limit`)
What implements this interface?	`gosymdb implementors --iface <name> --json`
What breaks if I change this?	`gosymdb blast-radius --symbol <fqname> --json`
List all packages	`gosymdb packages --json`
Index quality report	`gosymdb health --json`
Dead code candidates	`gosymdb dead --pkg <prefix> --json`
Where is this type used?	`gosymdb references --symbol <name> --json`

Read the full file on GitHub · 100 lines

Changes

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.

2mo ago First seen · 100 lines · 1,400 tokens per session scan A e3205823728c

Subscribe to this mod's changes

gosymdb CLAUDE.md is an instructions file published in the GitHub repository walkindude/gosymdb (18 stars, last pushed 27d ago), licensed Apache-2.0. It adds 1,400 tokens to every session, about $0.0056 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-30.

call-graph cli code-navigation dead-code developer-tools go

gosymdb CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gosymdb CLAUDE.mdwalkindude/gosymdb	Instructions file	18	27d ago	Apache-2.0	A	1,400	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

gosymdb: Instructions file for Claude Code