Borrowing it
Nothing to install: this file belongs to ngvoicu/kluris. 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/ngvoicu/kluris/main/CLAUDE.mdgit clone --depth 1 https://github.com/ngvoicu/klurisWrote 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/ngvoicu/kluris/claude-md)<a href="https://agentmods.dev/instructions/ngvoicu/kluris/claude-md"><img src="https://agentmods.dev/badge/instructions/ngvoicu/kluris/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.03398 | $0.03398 |
| Opus 5 | $0.01699 | $0.01699 |
| Sonnet 5 | $0.00680 | $0.00680 |
| Haiku 4.5 | $0.00340 | $0.00340 |
Grade A, and why
kluris 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 8d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
What This Is
Kluris turns AI agents into team subject matter experts by giving them shared, human-curated knowledge stored in git-backed brains.
Kluris = the tool. A brain = the git repo it creates.
Knowledge base
Read and write to the ngvoicu-sme brain through kluris (never edit brain
files by hand). Use the /kluris-ngvoicu-sme skill — search, learn, remember,
create.
Topics relevant to this repo: kluris-cli overview, architecture, multi-brain resolver, agent skills, kluris-pack, wake-up protocol, testing, CI/CD, deprecation.
Build & Test
source .venv/bin/activate # or: pipx install -e .
pip install -e ".[dev]" # dev install with pytest
pytest tests/ -v # run all tests (979 tests)
pytest tests/ --cov=kluris -q # with coverage (90%+)
pytest tests/test_create.py -v # single test file
Architecture
src/kluris/
cli.py # Click CLI -- all 13 commands in one file (incl. search, wake-up, pack, register, companion)
core/
config.py # Pydantic models (GlobalConfig, BrainConfig, BrainEntry)
brain.py # BRAIN_TYPES, scaffold_brain(), validate_brain_name()
maps.py # generate_brain_md(), generate_map_md() -- auto-generated files
frontmatter.py # read_frontmatter(), write_frontmatter(),
# update_frontmatter(path, patch, *, preloaded=(meta, body)?)
linker.py # validate_synapses(), validate_bidirectional(), detect_orphans(),
# detect_deprecation_issues(), check_frontmatter() with type validation
search.py # _collect_searchable(), _score_hit(), _matched_fields(),
# _extract_snippet(), search_brain() -- backs `kluris search`
mri.py # build_graph(), generate_mri_html() -- standalone HTML viz
git.py # git_init(), git_add(), git_commit(), git_log(),
# git_log_file_dates() batch helper (one subprocess replaces 2N)
agents.py # AGENT_REGISTRY (9 agents), per-brain SKILL.md renderer
# (always kluris-<name>, even for one brain);
# brain_path emitted in POSIX form (C:/ on Windows) for bash
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.
- 8d ago First seen · 166 lines · 3,398 tokens per session scan A 6a8e91de8d7c
kluris CLAUDE.md is an instructions file published in the GitHub repository ngvoicu/kluris (7 stars, last pushed 2mo ago), licensed MIT. It adds 3,398 tokens to every session, about $0.0170 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
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.