Borrowing it
Nothing to install: this file belongs to EliaCinti/wadachi. 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/EliaCinti/wadachi/main/CLAUDE.mdgit clone --depth 1 https://github.com/EliaCinti/wadachiWrote 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/eliacinti/wadachi/claude-md)<a href="https://agentmods.dev/instructions/eliacinti/wadachi/claude-md"><img src="https://agentmods.dev/badge/instructions/eliacinti/wadachi/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.00346 | $0.00346 |
| Opus 5 | $0.00173 | $0.00173 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
wadachi 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.
What it actually says
Wadachi — Session Rules
You have access to Wadachi, a persistent memory system via MCP. Use it.
Session Start (MANDATORY)
- Call
get_contextwith the current working directory and a brief task description. - Read the returned memories and decisions before touching any files.
- If you see relevant memories, use
get_memoryto load full content when needed.
During Work
- Before investigating something: call
recallfirst — you might already know it. - When you figure something out (a bug, a pattern, a config quirk): call
store_memoryimmediately. - When choosing between approaches: call
store_decisionwith rationale and rejected alternatives.
Session End
- Store anything you learned that would help a fresh session start faster.
- Architecture changes, new patterns, gotchas, and environment details are especially valuable.
Memory Categories
Use the right category for better retrieval:
architecture— system design, structure, patternsbugfix— bugs found + solutionsconfig— setup, env vars, infrastructurepattern— code conventions, recurring patternscontext— general project backgroundreference— API details, library notesnote— everything else
Tags
Always include 3-5 relevant tags when storing memories. Think: what words would you search for to find this again?
Project Scoping
If get_context detects a project, scope your store_memory and store_decision calls to that project name.
If no project is detected, use register_project to set one up.
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 · 35 lines · 346 tokens per session scan A bd3bf527307d
wadachi CLAUDE.md is an instructions file published in the GitHub repository EliaCinti/wadachi (0 stars, last pushed yesterday), licensed MIT. It adds 346 tokens to every session, about $0.0017 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
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.
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).
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).
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.
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.