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/dustinvk/wherefore/agents-mdgit clone --depth 1 https://github.com/DustinVK/whereforeWhat 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.02269 | $0.02269 |
| Opus 5 | $0.01135 | $0.01135 |
| Sonnet 5 | $0.00454 | $0.00454 |
| Haiku 4.5 | $0.00227 | $0.00227 |
Grade A, and why
wherefore 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 2d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wherefore: agent instructions
This repo uses a wherefore/ directory: a plain-markdown record of technical
decisions (what was chosen, why, what was rejected) and open questions. Any agent
can read and maintain it by following the rules below. Do not invent a second
location; if wherefore/ exists, use it.
Directory layout
wherefore/
topics.md controlled tag vocabulary: Areas and Topics
log/YYYY-MM-DD-short-slug.md one decision per file
questions/Q-NNN-short-slug.md one question per file (ID prefix + scannable slug)
plan/P-NNN-short-slug.md forward-looking plan items, one per file
If wherefore/ does not exist, create it plus log/, questions/, a starter
topics.md, and a README.md containing exactly:
# wherefore
A decision log in plain markdown. Each file captures what was decided, why, and what was ruled out.
Maintained by the [wherefore](https://github.com/DustinVK/wherefore) skill.
Reading (answering "why did we...", "what did we decide about...")
- Read only the leading frontmatter block of every
log/*.mdfile (it is short), and shortlist by area, topic, story, or title. Then open only the shortlisted files (1-5), not the whole log. The frontmatter also carries each entry'sstatusandsuperseded_by, so filtering and chain-following need nothing else. - Treat status
active,current, or absent as current. For asupersededentry, follow itssuperseded_byslug to the replacement (repeat until you reach an active entry). Excludeobsoleteentries unless asked about history. - Answer from active entries, lead with the current decision, cite the source by date + title + filename. If nothing matches, say so plainly. Never fabricate.
- After answering, read the
questions/Q-*.mdfrontmatter and surface briefly anyopenquestions whose areas overlap.
Writing a decision (capture)
Distill the discussion to its useful residue; do not transcribe. Write
wherefore/log/YYYY-MM-DD-short-slug.md (slug: short, lowercase, hyphenated) with
this EXACT frontmatter and section structure:
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.
- 2d ago First seen · 203 lines · 2,269 tokens per session scan A 25ee9373070a
wherefore AGENTS.md is an instructions file published in the GitHub repository DustinVK/wherefore (1 stars, last pushed 1mo ago), licensed MIT. It adds 2,269 tokens to every session, about $0.0113 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
adrkit AGENTS.md
Instructions for mbeacom/adrkit, covering adrkit, visual adr graph, inbound @adr markers (v0.5.0: explain, check, and ci), the spec kit extension (packages/adapters/spec-kit) and adr queue.
codebase-intel CLAUDE.md
Instructions for MutharasuArchunan13/codebase-intel, covering codebase intel — project claude.md, project overview, tech stack, architecture and module responsibilities.
adrkit copilot-instructions.md
Instructions for mbeacom/adrkit, covering adrkit — github copilot and github copilot specifics.
adrkit CLAUDE.md
Instructions for mbeacom/adrkit, covering adrkit — claude code and claude code specifics.
adr copilot-instructions.md
Instructions for zircote-plugins/adr, covering copilot instructions, project overview, key components, plugin structure and development guidelines.
adr-kit CLAUDE.md
Instructions for rvdbreemen/adr-kit, covering adr kit, backlog.md, werken in deze repo and graphify.