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/2389-research/ccvault/claude-mdgit clone --depth 1 https://github.com/2389-research/ccvaultWrote 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/2389-research/ccvault/claude-md)<a href="https://agentmods.dev/instructions/2389-research/ccvault/claude-md"><img src="https://agentmods.dev/badge/instructions/2389-research/ccvault/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.00419 | $0.00419 |
| Opus 5 | $0.00210 | $0.00210 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
ccvault 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 5d 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
ccvault - Claude Code Conversation Vault
Names
- AI: VaultMaster 3000
- Human: The Harp-Dawg Supreme
Project Overview
ccvault is a Go application that archives Claude Code conversations from ~/.claude for offline search, analytics, and MCP integration. Based on msgvault.
Architecture
~/.claude/projects/<encoded-path>/<uuid>.jsonl → SQLite + FTS5 + Parquet
Key components:
- Parser: Reads JSONL session files from Claude Code
- SQLite + FTS5: Full-text search with triggers
- DuckDB + Parquet: Fast analytics queries
- Bubble Tea: Terminal UI
- MCP Server: AI integration via JSON-RPC
Development
# Build
make build
# Run tests
make test
# Sync and explore
make sync
make tui
# Build analytics cache
make cache
Key Files
cmd/ccvault/main.go- CLI entry pointpkg/parser/- JSONL parsingpkg/models/- Data structuresinternal/config/- Configuration managementinternal/db/- SQLite + FTS5 layerinternal/sync/- Incremental sync logicinternal/search/- Query parsing and executioninternal/export/- Markdown exportinternal/tui/- Terminal UIinternal/mcp/- MCP serverinternal/analytics/- DuckDB/Parquet
Important Notes
- Session files are JSONL with nested message structures
- Project paths in Claude use dash-separated encoding of filesystem paths (slashes become dashes), with URL encoding for special characters
- FTS5 uses triggers to auto-sync with turns table
- Incremental sync tracks file modification times
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.
- 5d ago First seen · 61 lines · 419 tokens per session scan A 3f9bb8c69063
ccvault CLAUDE.md is an instructions file published in the GitHub repository 2389-research/ccvault (10 stars, last pushed 22d ago), licensed MIT. It adds 419 tokens to every session, about $0.0021 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
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).