codedb is a code-intelligence server that indexes software projects so AI agents can search files, symbols, callers, dependencies, and structural outlines. It is for coding agents that need context about a codebase through MCP or HTTP while leaving file editing to native tools. Its catalogue instructions help agents use codedb's code-understanding tools.
Borrowing it
Nothing to install: this file belongs to justrach/codedb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/justrach/codedb/main/CLAUDE.mdgit clone --depth 1 https://github.com/justrach/codedbWrote 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/justrach/codedb/claude-md)<a href="https://agentmods.dev/instructions/justrach/codedb/claude-md"><img src="https://agentmods.dev/badge/instructions/justrach/codedb/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.
<a href="https://agentmods.dev/instructions/justrach/codedb/claude-md"><img src="https://agentmods.dev/badge/instructions/justrach/codedb/claude-md.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.00412 | $0.00412 |
| Opus 5.5 | $0.00165 | $0.00165 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
codedb 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 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.
What it actually says
codedb — Agent Instructions
Project
Zig 0.16.x code intelligence server. Tests live in the split src/test_*.zig files — one binary per area (see build.zig). Build and test with zig build test; run a single binary with e.g. zig build test-index.
Rules
Filing Issues
Every GitHub issue must include a failing test case. No exceptions.
When creating an issue:
- Write a
test "issue-XX: <description>"block in the matchingsrc/test_*.zigfile (e.g.src/test_index.zigfor index bugs) that fails on the currentmainbranch - Verify it fails:
zig build test 2>&1 | grep "issue-XX" - File the issue via
gh issue createwith this structure:- Title:
<module>: <concise description> - Body sections: Problem, Failing Test (the zig test block), Expected, Fix
- Labels:
bugfor defects,priority:p0for crashes,priority:p2for correctness
- Title:
- Commit the failing test on a branch:
issue-XX-failing-test - Do not fix the bug in the same commit as the failing test
If you cannot write a failing test, the issue is not well-defined enough to file.
Test Style
- Use
std.testingandtesting.allocator - Use
std.heap.ArenaAllocatorfor Explorer tests - Always
defercleanup (arena.deinit, allocator.free) - One test per issue, named
test "issue-XX: <short description>" - Keep tests minimal — only exercise the specific broken code path
Code Style
- No comments or documentation changes unless explicitly asked
- Prefer minimal, targeted fixes over refactors
- Follow existing patterns in the module you're editing
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 · 39 lines · 412 tokens per session scan A 36b4b39771eb
codedb CLAUDE.md is an instructions file published in the GitHub repository justrach/codedb (1,397 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 412 tokens to every session, about $0.0016 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.