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/adammagued/kim/agents-mdgit clone --depth 1 https://github.com/AdamMagued/kimWrote 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/adammagued/kim/agents-md)<a href="https://agentmods.dev/instructions/adammagued/kim/agents-md"><img src="https://agentmods.dev/badge/instructions/adammagued/kim/agents-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 | $0.00645 | $0.00645 |
| Opus 5 | $0.00322 | $0.00322 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
kim AGENTS.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.
Copies of this mod
1 near-identical copy found in the catalogue:
- kim CLAUDE.md — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Kim Agent Platform (root router)
What this is
Kim is a local AI agent platform (Tauri + React frontend, Python orchestrator, MCP server).
Real app root is kim-pro/. Never modify anything outside kim-pro/.
Standing constraints (never violate)
- Code tab must NEVER use OpenAI auth or gpt-5.5 — only ollama cloud or browser provider.
- CSS import order in
desktop/src/index.cssis load-bearing (cascade). Do not reorder. - System-prompt f-strings: examples inside f-strings need doubled braces
{{ }}. - After any Rust change,
tauri devneeds a restart (hot-reload does not apply to Rust). - Secret-file sandbox:
mcp_server/config.validate_path()denies secret files (.env,.env.*,*.pem,*.key,id_rsa*,id_ed25519*,credentials,.npmrc,.pypirc) at any depth and sensitive dirs (.ssh,.aws, browser profiles, cloud SDKs, …). Don't weaken these globs/paths. Note: enforcement is filename/dir-based, not a content scanner — secrets pasted into a normally-named file are not caught.
Architecture pointer
See ARCHITECTURE.md for the full layer diagram and IPC protocol spec.
See ROADMAP.md for the current work backlog and sequencing (it points at the
active plan, docs/ROADMAP_TO_10.md).
Per-directory guides (load only the one you need)
| Directory | Guide | What's there |
|---|---|---|
orchestrator/ |
orchestrator/CLAUDE.md |
Agent loop, providers, session store |
mcp_server/ |
mcp_server/CLAUDE.md |
50+ OS-control tools, tool registry |
desktop/src/ |
desktop/src/CLAUDE.md |
React UI, IPC event consumers |
desktop/src-tauri/ |
desktop/src-tauri/CLAUDE.md |
Rust shell, subprocess mgmt |
How-to recipes
HOW_TO.md — exact minimal file sets for common change patterns.
Finding things fast
- Know which file → open it directly.
- Don't know → grep/find with a targeted pattern.
- Never do a broad full-repo sweep as a first move.
Test commands (all four suites — cli/ is a separate crate, easy to forget)
python -m pytest tests/ # Python tests (venv required)
cd desktop && npx tsc --noEmit && npm run test # Vitest tests
cd desktop/src-tauri && cargo test # Rust tests (desktop)
cd cli && cargo test # Rust tests (kim CLI)
After every push, confirm the remote CI run is green: gh run list --limit 1.
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 · 47 lines · 645 tokens per session scan A ba79327632d6
kim AGENTS.md is an instructions file published in the GitHub repository AdamMagued/kim (5 stars, last pushed 1mo ago), licensed MIT. It adds 645 tokens to every session, about $0.0032 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
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.