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.
npx agentmods add instructions/mav-rik/kb-cli/claude-mdgit clone --depth 1 https://github.com/mav-rik/kb-cliWhat 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 | $0.01048 | $0.01048 |
| Opus 5 | $0.00524 | $0.00524 |
| Sonnet 5 | $0.00210 | $0.00210 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade C, and why
kb-cli CLAUDE.md scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
pnpm clean # rm -rf dist How it starts
The opening of the file, as written. The whole thing — 78 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.
Build & Development
pnpm build # rolldown → dist/main.js (ESM bundle)
pnpm test # vitest run (all tests)
pnpm dev # build + run CLI
pnpm clean # rm -rf dist
Run a single test file: npx vitest run tests/remote-config.test.ts
The CLI entry point is bin.js → dist/main.js. After building, test locally with node ./dist/main.js <command>.
Architecture
Framework: moostjs — decorator-driven CLI (@moostjs/event-cli) and HTTP (@moostjs/event-http) framework. Controllers use @Cli(), @Param(), @CliOption(), @Description() decorators.
Build: Rolldown bundles src/main.ts into a single ESM file. The unplugin-atscript plugin compiles .as model files. All heavy dependencies are externalized (not bundled).
Data storage: ~/.kb/ directory. Each wiki is ~/.kb/{name}/docs/ (markdown files) + index.db (SQLite for metadata, FTS5, vectors, links). Markdown files are source of truth; SQLite is a rebuildable index.
Key layers
Controllers (CLI commands)
↓ resolveWiki() → WikiRef (local or remote)
WikiGateway → getOps(ref) → WikiOps interface
├── LocalWikiOps → existing services (storage, search, index, workflow)
└── RemoteWikiOps → RemoteClient → HTTP to remote kb server
WikiRef routing: ConfigService.resolveWiki() returns a discriminated union ({ type: 'local' | 'remote', ... }). The gateway creates the appropriate ops implementation. Controllers don't know or care whether a wiki is local or remote.
ApiController is NOT routed through the gateway — it always operates locally because it IS the remote endpoint that RemoteClient calls.
Services (src/services/)
container.ts— singleton DI container, instantiates all servicesconfig.service.ts— global config + CWD config walking + wiki resolutionremote-config.service.ts— manages~/.kb/remotes.json(cached in memory)storage.service.ts— markdown file read/write (sync, filesystem)index.service.ts— atscript-db with SQLite (documents, links, chunks tables)fts.service.ts— raw SQL FTS5 table (not contentless; BM25 with weights)vector.service.ts— raw sqlite-vec for embeddings (delete+insert pattern, not REPLACE)embedding.service.ts— lazy HuggingFace all-MiniLM-L6-v2 (384-dim, cached in ~/.kb/.models/)search.service.ts— hybrid search via Reciprocal Rank Fusion (RRF)doc-workflow.service.ts— orchestrates index+FTS+vector operationswiki-ops.ts— WikiOps interface + LocalWikiOps + RemoteWikiOpswiki-gateway.service.ts— routes WikiRef to correct ops implementationremote-client.ts— HTTP client (native fetch) for remote API calls
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.
- 3d ago First seen · 78 lines · 1,048 tokens per session scan C 6dead57f8b05
kb-cli CLAUDE.md is an instructions file published in the GitHub repository mav-rik/kb-cli (12 stars, last pushed 3mo ago), licensed MIT. It adds 1,048 tokens to every session, about $0.0052 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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).
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.
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.
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).
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.