Borrowing it
Nothing to install: this file belongs to mduongvandinh/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/mduongvandinh/llm-wiki/main/AGENTS.mdgit clone --depth 1 https://github.com/mduongvandinh/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/mduongvandinh/llm-wiki/agents-md)<a href="https://agentmods.dev/instructions/mduongvandinh/llm-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/mduongvandinh/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/mduongvandinh/llm-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/mduongvandinh/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.02037 | $0.02037 |
| Opus 5 | $0.01019 | $0.01019 |
| Sonnet 5 | $0.00407 | $0.00407 |
| Haiku 4.5 | $0.00204 | $0.00204 |
Grade A, and why
llm-wiki 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki — Agent Instructions
For: Cursor, Windsurf, Codex CLI, Aider, Continue.dev, and any agent that reads AGENTS.md Claude Code users: see CLAUDE.md and install the skill from skills/llm-wiki/
You are maintaining a personal knowledge base using the LLM Wiki pattern. The wiki builds itself: you read raw sources, write structured wiki pages, maintain cross-references, detect contradictions, and keep everything up to date. The human only reads the wiki and asks questions.
3-Layer Architecture
raw/ → Raw sources (IMMUTABLE — you READ ONLY, NEVER modify)
wiki/ → Wiki you write and maintain entirely
outputs/ → Query results, reports, battlecards, briefs
config.yaml → Topics, feeds, schedule
Golden Rules
- raw/ is immutable. Never edit, delete, or move files in raw/. It is the source of truth.
- You own wiki/ entirely. The human does not manually edit wiki pages.
- One file per topic. Each entity, concept, and source summary is a separate .md file. Filename: kebab-case.
- Cross-reference everything. Use
[[filename]]links. Every page needs at least 2 links to other pages. - Keep INDEX.md current. Create/delete a wiki page → update INDEX.md immediately.
- Log all activity. Every action gets an entry in wiki/LOG.md.
How to Run Each Workflow
When the user asks you to run the wiki, follow these workflows. Use natural language descriptions of what you're doing — you don't have a slash command, just execute the steps directly.
Run full cycle (discover → ingest → lint)
- Read
config.yamlto understand topics, feeds, and settings - Run discover: search for new sources based on topics/gaps
- Run ingest: process all new files in
raw/ - Run lint: health check the wiki
- Report summary
Ingest
- Read
config.yamlandAGENTS.md(this file) for schema and rules - Read
.discoveries/history.json→ get list of already-processed files - Scan
raw/→ find files not in history - For each new file:
a. Read full content
b. Create source summary →
wiki/sources/c. Extract entities → create/updatewiki/entities/d. Extract concepts → create/updatewiki/concepts/e. Add[[cross-references]]to related pages f. Flag contradictions with existing content - Update
wiki/INDEX.md - Append to
wiki/LOG.md - Update
.discoveries/history.json
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.
- 10d ago First seen · 280 lines · 2,037 tokens per session scan A b2badd64349d
llm-wiki AGENTS.md is an instructions file published in the GitHub repository mduongvandinh/llm-wiki (213 stars, last pushed 4mo ago), licensed MIT. It adds 2,037 tokens to every session, about $0.0102 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.
Other instructions, from other repositories
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.
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.
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.
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).
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.