Kami CLAUDE.md

Repository instructions for Kami, a document-generation system with HTML templates and pipelines that build PDFs, presentations, and PNG images. They explain where project files live and how Claude-specific workflows fit together.

In plain words
What is it for?
Use them when creating documents, editing templates, checking generated metadata, troubleshooting rendering, or preparing a release.
Why use it?
They help an AI coding agent follow the repository's maintenance, writing, rendering, and release rules without relying on outdated notes.

Instructions file

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/tw93/kami/claude-md
Clone the repo
git clone --depth 1 https://github.com/tw93/Kami
Per session 379 This file is loaded in full into every session.
When invoked 379 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.00379 $0.00379
Opus 5 $0.00189 $0.00189
Sonnet 5 $0.00076 $0.00076
Haiku 4.5 $0.00038 $0.00038

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

Security

Grade A, and why

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

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 · 17 lines

What it actually says

Kami

Document-generation skill and template system. Editorial HTML templates plus a PDF / PPTX / PNG build pipeline.

Where things live

  • AGENTS.md owns every repository maintenance rule: repo map, working rules, generated mirrors, packaging hard stops, CI gotchas, risk areas, verification, fonts. This file does not restate them. The Claude-specific section below is the only overlap, and it exists because those steps are Claude-side workflow rather than repository policy.
  • Producing a document: SKILL.md is the runbook. Template design spec: references/design.md. Writing spec: references/writing.md. Draft review checklist: references/anti-patterns.md. Render troubleshooting: references/production.md Part 4. Release flow: docs/release.md.
  • python3 scripts/build.py --help is the authoritative command list. Do not trust a hand-written copy; the Commands section in AGENTS.md covers only the scripts --help cannot reach.

Claude-specific

  • This repo ships plugins for both Claude Code and Codex. plugins/kami/ and .claude-plugin/marketplace.json are generated: after editing a root file, run python3 scripts/build_metadata.py --check.
  • The Claude Desktop skill package must be the output of bash scripts/package-skill.sh (top-level kami/ directory, 6 MB ceiling). A hand-zipped checkout is rejected on size.
  • To let Claude drive rendering and verification directly: claude mcp add kami -- python3 <checkout>/scripts/mcp_server.py.
  • Plugin install changes need an isolated smoke run: under HOME=/tmp/..., claude plugin marketplace add <path> then claude plugin install kami@kami. Reading metadata is not verification.
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. 3d ago First seen · 17 lines · 379 tokens per session scan A db6754b28968

Subscribe to this mod's changes

Kami CLAUDE.md is an instructions file published in the GitHub repository tw93/Kami (11,071 stars, last pushed yesterday), licensed MIT. It adds 379 tokens to every session, about $0.0019 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.

Related

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

microsoft/vscode · 6,785 tokens

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

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