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/helicerat/llm-wiki-loop/claude-mdgit clone --depth 1 https://github.com/helicerat/llm-wiki-loopWrote 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/helicerat/llm-wiki-loop/claude-md)<a href="https://agentmods.dev/instructions/helicerat/llm-wiki-loop/claude-md"><img src="https://agentmods.dev/badge/instructions/helicerat/llm-wiki-loop/claude-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.00983 | $0.00983 |
| Opus 5 | $0.00491 | $0.00491 |
| Sonnet 5 | $0.00197 | $0.00197 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
llm-wiki-loop 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 5d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema
This file is the contract. It holds only rules that cause damage if forgotten mid-session,
because this is the file that survives context compaction. Everything else lives in
wiki/index.md, which may compress away and be re-read on demand.
Layers
raw/ — sources. Read them, never write to them, never move a file out of wiki/ back
into raw/. Ingestion is one-way. This boundary is a directory, not a request, because the
failure it prevents — silently rewriting a source to match a summary — is invisible once it
happens.
wiki/ — yours entirely. Create pages, update them, maintain cross-references.
outcomes/ — append-only. What shipped, and what happened afterward. Never edit a past
entry; correct it with a new one.
The claim contract
Every claim page carries:
claim: one sentence, falsifiable
status: candidate | rule | retired
n: 0
effect: observed magnitude, with units
form: timeless | snapshot | pointer
as_of: YYYY-MM-DD
provenance: extracted | inferred | ambiguous
outcomes: []
n is not editable by hand. It is incremented only by wiki-measure, only from an
entry in outcomes/. A claim whose n cannot be reconstructed from the outcome log is a
lint error, not a rounding difference.
State transitions, mechanical, no judgement:
candidate→ruleatn >= 3rule→retiredwhen the three most recent outcomes contradict it- nothing is deleted, ever. Retired claims keep their history
Only status: rule may block a draft. Candidates are reported and never enforced. This
is the whole discipline: an untested observation does not get to overrule you.
Three legal forms for a fact
- timeless — does not decay. No stamp needed
- snapshot — dated observation. Requires
as_of - pointer — names where the truth actually lives. Requires a resolvable target
A present-tense quantitative claim about something volatile, carrying neither as_of nor
pointer form, is a lint error. Anything inside a dated container is exempt structurally and
needs no annotation.
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.
- 5d ago First seen · 107 lines · 983 tokens per session scan A a4b89b8b43d8
llm-wiki-loop CLAUDE.md is an instructions file published in the GitHub repository helicerat/llm-wiki-loop (6 stars, last pushed 1mo ago), licensed MIT. It adds 983 tokens to every session, about $0.0049 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.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.