agentmods.dev

kiri CLAUDE.md

Instructions for working in the CAPHTECH/kiri project, including required use of KIRI's code-search and code-reading tools.

In plain words
What is it for?
They help agents understand the codebase, search for files and patterns, read selected code sections, and trace dependencies.
Why use it?
They make the project's preferred exploration workflow clear and help agents find relevant code without scanning everything.

Instructions file

155 6mo ago A scan 4,012 tokens original MIT
View the source file CAPHTECH/kiri
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/caphtech/kiri/claude-md
Clone the repo
git clone --depth 1 https://github.com/CAPHTECH/kiri
Per session 4,012 This file is loaded in full into every session.
When invoked 4,012 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.04012 $0.04012
Opus 5 $0.02006 $0.02006
Sonnet 5 $0.00802 $0.00802
Haiku 4.5 $0.00401 $0.00401

Measured 2d ago against content hash c26962095aa3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

kiri 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 2d 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.

CLAUDE.md · 401 lines

How it starts

The opening of the file, as written. The whole thing — 401 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.

Use KIRI MCP Tools - MANDATORY

This project uses KIRI MCP. You MUST proactively use KIRI MCP tools for all code exploration and search tasks.

When to Use KIRI Tools

ALWAYS use KIRI tools instead of Glob/Grep for:

  1. Understanding codebase structure → Use mcp__kiri__context_bundle

    • Finding relevant code for implementing features
    • Understanding how existing features work
    • Locating code related to specific functionality
    • Example: mcp__kiri__context_bundle with goal "How does the daemon lifecycle work?"

  2. Searching for files or code patterns → Use mcp__kiri__files_search

    • Finding files by keywords or functionality
    • Locating implementation patterns
    • Example: mcp__kiri__files_search with query "daemon startup"

  3. Reading specific code sections → Use mcp__kiri__snippets_get

    • Reading only relevant parts of large files
    • Minimizing token usage
    • Example: mcp__kiri__snippets_get for path "src/daemon/daemon.ts"

  4. Understanding dependencies → Use mcp__kiri__deps_closure

    • Finding what files depend on a module (inbound)
    • Finding what a module depends on (outbound)
    • Impact analysis for refactoring
    • Example: mcp__kiri__deps_closure with path "src/server/runtime.ts"

  5. Refining search results → Use mcp__kiri__semantic_rerank

    • Prioritizing files by semantic relevance
    • Narrowing down search results

Performance Benefits

  • Token efficiency: KIRI returns only relevant snippets, not entire files
  • Precision: Context-aware search beats simple pattern matching
  • Speed: Indexed search is faster than filesystem traversal
  • Structure-aware: Understands code symbols and dependencies

Token-Saving Workflow (v0.9.6+)

  1. Run files_search or context_bundle with compact: true to gather lightweight candidates.
  2. Use snippets_get with compact: true when you only need metadata, or includeLineNumbers: true when copying exact line references (format: 1375→export function ...).
  3. Request includeTokensEstimate: true on context_bundle only when you explicitly need the projected token count; it is skipped by default.

Read the full file on GitHub · 401 lines

Changes

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.

  1. 2d ago First seen · 401 lines · 4,012 tokens per session scan A c26962095aa3

Subscribe to this mod's changes

kiri CLAUDE.md is an instructions file published in the GitHub repository CAPHTECH/kiri (155 stars, last pushed 6mo ago), licensed MIT. It adds 4,012 tokens to every session, about $0.0201 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.

ProductivityResearch
Related

Other instructions, from other repositories

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens