LLM Wiki is a system that uses AI agents to research sources, compile knowledge bases, organize project briefs, and answer questions from the resulting wiki. It is used to turn rough ideas and investigations into structured, reusable knowledge for agents, including Claude Code, Codex, and OpenCode. The catalogue entries are commands, hooks, skills, instructions, and a plugin that implement its workflow.
Borrowing it
Nothing to install: this file belongs to nvk/llm-wiki. 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/nvk/llm-wiki/master/AGENTS.mdgit clone --depth 1 https://github.com/nvk/llm-wikiWrote 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/nvk/llm-wiki/agents-md)<a href="https://agentmods.dev/instructions/nvk/llm-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/nvk/llm-wiki/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/nvk/llm-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/nvk/llm-wiki/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.14206 | $0.14206 |
| Opus 5.5 | $0.05682 | $0.05682 |
| Sonnet 5.5 | $0.02841 | $0.02841 |
| Haiku 4.5 | $0.01421 | $0.01421 |
Grade A, and why
llm-wiki AGENTS.md scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
and IPv4 retry (`curl -4`) when media hosts hang on IPv6. How it starts
The opening of the file, as written. The whole thing — 1,091 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki — Agent Instructions
This is an "idea file" in the spirit of Karpathy's LLM Wiki. Paste it into any LLM agent (OpenAI Codex, Claude Code, OpenCode, Gemini Code Assist, or similar) and it will build and manage a wiki for you. The agent customizes the specifics; this file communicates the system.
Editing the llm-wiki repo itself? This file is the portable wiki protocol for end users. The dev contract for the plugin codebase (testing, sync workflow, project structure, symlink invariant) lives in
CLAUDE.md— read it in addition to this file. Both Claude Code and Codex agents working on the repo should treatCLAUDE.mdas the source of truth for repo-level workflow.
What This Is
An LLM-compiled knowledge base. You (the LLM agent) are both the compiler and the query engine. Raw source documents are ingested, then incrementally compiled into a wiki of interconnected markdown articles. The human rarely edits the wiki directly — that's your domain.
The metaphor: raw sources are source code, you are the compiler, the wiki is the executable.
Architecture
Hub Path
Defaults to ~/wiki/. Optionally configured via ~/.config/llm-wiki/config.json:
{ "hub_path": "~/Library/Mobile Documents/com~apple~CloudDocs/wiki" }
If the config exists, prefer hub_path (expand only the leading ~) instead of
~/wiki/ everywhere below. Treat resolved_path from older configs as a
machine-specific fallback cache, not as the source of truth; do not write it
into shared configs. If the path can be statted but reading wikis.json or
listing topics/ fails with Operation not permitted, the path is correct and
macOS/iCloud privacy is blocking the launcher; ask the user to grant Full Disk
Access or iCloud Drive access and restart, rather than falling back to another
machine path. Store the selected path as HUB. Use
/wiki config hub-path <path> to set it up, or create the JSON manually.
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 Changed · +21 lines · +329 tokens per session 9c268ff1673c
- 5d ago Changed · +12 tokens per session 12a6c810ba13
- 24d ago Changed · +10 lines · +136 tokens per session 6e16e7dc405d
- 1mo ago Changed · +14 tokens per session ec87cb98d9cd
- 1mo ago First seen · 1,060 lines · 13,715 tokens per session scan A 4ce9eaf3607a
llm-wiki AGENTS.md is an instructions file published in the GitHub repository nvk/llm-wiki (1,466 stars, last pushed 2d ago), licensed MIT. It adds 14,206 tokens to every session, about $0.0568 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.