Borrowing it
Nothing to install: this file belongs to varun29ankuS/shodh-memory. 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/varun29ankuS/shodh-memory/main/CLAUDE.mdgit clone --depth 1 https://github.com/varun29ankuS/shodh-memoryWrote 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/varun29ankus/shodh-memory/claude-md)<a href="https://agentmods.dev/instructions/varun29ankus/shodh-memory/claude-md"><img src="https://agentmods.dev/badge/instructions/varun29ankus/shodh-memory/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.00532 | $0.00532 |
| Opus 5 | $0.00266 | $0.00266 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
shodh-memory 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 7d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shodh-Memory Project Instructions
MUST Rules
- MUST NOT run
cargo buildorcargo rununless the user explicitly asks. Onlycargo check,cargo clippy, andcargo testare allowed by default. - MUST NOT add "Co-Authored-By" or "Generated with Claude Code" to commits. Clean commit messages only.
- MUST NOT comment on GitHub issues/PRs without showing user a draft first.
- MUST NOT create git worktrees outside the project folder. All worktrees go in
<repo>/.claude/worktrees/<name>. NeverC:/smt, never~/.claude/worktrees, never a sibling directory. A worktree outsidekalki-v2/misses the parent.cargo/config.toml, builds to a different artifact path, and silently forkstarget/into two complete trees. - MUST remove a worktree once its branch is merged or abandoned. Before removing one, run
git status --porcelainin it and confirm any untracked files exist in git — untracked content is the only thinggit worktree removecannot recover, since branch refs survive removal.
Code Standards
- IMPORTANT: Production grade code only. No TODOs, no placeholders, no mocks, no stubs.
- IMPORTANT: Understand architecture and data flow before fixing anything. Read files before editing.
- IMPORTANT: No assumptions. Always read the actual source code to verify API shapes, response fields, status codes, endpoint methods, and data structures before writing code or tests against them. Never guess.
- All changes go through PR workflow: branch → commit → push → PR → merge.
Persistent Memory (shodh-memory MCP)
You have session continuity via shodh-memory hooks. Key behaviors:
- Relevant memories surface automatically — don't manually "check" memory
- Use
remembersparingly (high-importance only),forgetfor corrections - Use
list_todosat session start for pending work - The memory system you're using IS this codebase
Codebase Map
src/— Rust core (memory, API server, embeddings, graph, vector search)mcp-server/— TypeScript MCP server (45 tools, index.ts)tui/— Rust TUI dashboardhooks/— Claude Code hooks for automatic memorypython/— Python bindings (PyO3/maturin)- Architecture: RocksDB + Vamana/SPANN vector search + knowledge graph with Hebbian learning
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.
- 7d ago First seen · 31 lines · 532 tokens per session scan A 8aa746bded0d
shodh-memory CLAUDE.md is an instructions file published in the GitHub repository varun29ankuS/shodh-memory (279 stars, last pushed today), licensed Apache-2.0. It adds 532 tokens to every session, about $0.0027 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
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.
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.
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).
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.