Borrowing it
Nothing to install: this file belongs to nico2sh/kimun. 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/nico2sh/kimun/main/CLAUDE.mdgit clone --depth 1 https://github.com/nico2sh/kimunWrote 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/nico2sh/kimun/claude-md)<a href="https://agentmods.dev/instructions/nico2sh/kimun/claude-md"><img src="https://agentmods.dev/badge/instructions/nico2sh/kimun/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.00598 | $0.00598 |
| Opus 5 | $0.00299 | $0.00299 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
kimun 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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kimun
A note taking app split into two components:
- core: all file operations, indexing, and note taking functionality
- ui (TUI): interaction and presentation layer only
Docs
The docs/ directory is the Kimün user-facing documentation site. Only end-user documentation belongs there. Plans, specs, and other internal working documents must be stored outside of docs/.
Rules
- All file modifications and path manipulation must be implemented in core, never in the TUI
- The TUI may still read files directly (
read_to_string,File::open,metadata) — those behave the same on every platform. What it must not do is callrename,copy,remove_file,remove_dir*,create_dir*,canonicalize,set_permissionsor a truncatingwrite: those go throughkimun_core::system. Enforced by.github/scripts/check-host-fs.pyin CI (seeadr/0044)
- The TUI may still read files directly (
- Never hardcode the
.mdextension or/path separator — use existing core functions for cleaning up note paths, removing extensions, or splitting paths into slices - If a new path or file operation is needed, implement it in core
- Core's public API must use
VaultPathfor vault-internal path arguments and return types — neverPathBuforPathfor note/directory operations within a vault- Configuration-level OS paths (workspace root, cache file, log directory) use
SystemPathfromkimun_core::system— absolute and normalized by construction. PlainPathBuf/Pathonly for raw, as-written config values before they are resolved, and for converting aVaultPathback to a real filesystem location
- Configuration-level OS paths (workspace root, cache file, log directory) use
- All direct filesystem operations (
std::fs,tokio::fs) in core must live inside one of two modules, never inlib.rsor elsewhere:nfs— vault-scoped: notes, attachments, backups inside a workspace, addressed byVaultPathsystem— host-scoped: the app's own directories, path resolution, cross-volume moves, atomic replace. Every OS-specific rule (verbatim Windows paths,EXDEVvsERROR_NOT_SAME_DEVICE,HOME/USERPROFILE) belongs here and nowhere else
- A workspace's index is
kimun_core::IndexFile, never a hand-built path: it owns the.kimuncachenaming and moves/removes its-wal/-shmsiblings with it - The
NoteVaultabstraction sits on top of the OS filesystem and must work on Windows, macOS, and Linux- Only accept characters valid on all three major filesystems
- Paths are case-insensitive; default to lowercase
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 · 27 lines · 598 tokens per session scan A 2458829ea9bd
kimun CLAUDE.md is an instructions file published in the GitHub repository nico2sh/kimun (56 stars, last pushed 18d ago), licensed MIT. It adds 598 tokens to every session, about $0.0030 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
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.