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/polarityinc/zenith/claude-mdgit clone --depth 1 https://github.com/Polarityinc/zenithWrote 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/polarityinc/zenith/claude-md)<a href="https://agentmods.dev/instructions/polarityinc/zenith/claude-md"><img src="https://agentmods.dev/badge/instructions/polarityinc/zenith/claude-md.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.1 | $0.02262 | $0.02262 |
| Opus 5 | $0.01131 | $0.01131 |
| Sonnet 5 | $0.00452 | $0.00452 |
| Haiku 4.5 | $0.00226 | $0.00226 |
Grade A, and why
zenith 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 6d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this repo is
ZenithDB — a Rust columnar database engine purpose-built for AI agent traces. 18-crate workspace, one cargo build. Engine name zenithdb, CLI binary zen, all crates prefixed zen_.
Toolchain
- Rust 1.87 stable, pinned via
rust-toolchain.toml(rustup will pick it up automatically). protoc3.21+ is required to build (brew install protobuf/apt-get install protobuf-compiler). Several crates runprost-build/tonic-buildin theirbuild.rs.
Common commands
CI runs four gates and rejects on any of them. Match them locally before pushing:
cargo fmt --all --check
cargo clippy --workspace --all-targets -- -D warnings # -D warnings is enforced
cargo test --workspace --all-features
cargo deny check # licenses + advisories
cargo audit --deny warnings runs in CI as a fifth gate.
Running a single test
cargo test -p <crate> <test_name> # unit/integration test in a crate
cargo test -p zen_format encoder::tests::roundtrip # by full path
cargo test -p integration auth:: # the integration suite lives in tests/integration
cargo test -p integration -- --nocapture # see println! / tracing output
The integration / perf / chaos suites are separate crates under tests/ (not cargo test default targets — they're listed in the workspace members). Always pass -p integration / -p perf / -p chaos to target them.
Run the server
# Default dev profile — SQLite catalog + local-FS object store under ./data/. Zero external services.
cargo run --release -p zen_cli -- serve --config examples/zenithdb.dev.toml
zen_cli ships two binaries: zen (the user-facing CLI with serve, bench, admin-backup, admin-restore, etc.) and zenithdb (server-only entrypoint). Both live in crates/zen_cli/src/.
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.
- 6d ago First seen · 154 lines · 2,262 tokens per session scan A 8de76d3e3e9a
zenith CLAUDE.md is an instructions file published in the GitHub repository Polarityinc/zenith (142 stars, last pushed 29d ago), licensed Apache-2.0. It adds 2,262 tokens to every session, about $0.0113 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-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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).