Borrowing it
Nothing to install: this file belongs to kavo-labs/kavo. 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/kavo-labs/kavo/main/CLAUDE.mdgit clone --depth 1 https://github.com/kavo-labs/kavoWrote 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/kavo-labs/kavo/claude-md)<a href="https://agentmods.dev/instructions/kavo-labs/kavo/claude-md"><img src="https://agentmods.dev/badge/instructions/kavo-labs/kavo/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.05048 | $0.05048 |
| Opus 5 | $0.02524 | $0.02524 |
| Sonnet 5 | $0.01010 | $0.01010 |
| Haiku 4.5 | $0.00505 | $0.00505 |
Grade A, and why
kavo 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What Kavo is
A production-grade CRUD framework for TypeScript: define an entity once (via TypeORM, Prisma, Mongoose, or MikroORM) and get the full REST CRUD surface — filtering, sorting, pagination, nested includes, field selection, optional per-operation DTOs, transactions, and problem-details errors — behind generated NestJS routes, configurable at global → entity → operation → per-call scope.
The authoritative sources are docs/ (architecture notes and ADRs) and the Conventions section below, which is normative — naming deviations are review findings. Consult the governing ADR before changing behavior it covers, rather than inventing behavior.
Commands
pnpm install
pnpm check # the full gate: generate (Prisma client + fixture schema) + build + typecheck + depcruise + lint + test (run before considering work done)
pnpm build # tsc -b (project references across the workspace — src only)
pnpm typecheck # tsc --noEmit over the root tests/ plus every package's and example's tests/ (tsconfig.tests.json)
pnpm test # vitest run (whole monorepo)
pnpm test:coverage # the same suite under v8 coverage, failing on the thresholds in vitest.coverage.config.ts — its own CI job, deliberately not part of `check`
pnpm depcruise # enforce package-boundary rules (.dependency-cruiser.cjs)
pnpm lint # oxlint over packages/*, examples/*, tests/ and .github/scripts/
pnpm prettify # prettier --write . (printWidth 120)
pnpm format:check # prettier --check . — the separate formatting job CI runs alongside the gate
pnpm docs:build # vitepress build docs — a second CI gate that `check` does NOT run
pnpm docs:links # every `docs/**.md` reference and sidebar link resolves (a third; also not in `check`)
Run a single test file or test by name:
pnpm vitest run packages/core/tests/filter-parser.spec.ts
pnpm vitest run -t "coerces JavaScript number syntax"
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 · 155 lines · 5,048 tokens per session scan A 3334d153c69e
kavo CLAUDE.md is an instructions file published in the GitHub repository kavo-labs/kavo (12 stars, last pushed today), licensed MIT. It adds 5,048 tokens to every session, about $0.0252 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-09-02.
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.