Borrowing it
Nothing to install: this file belongs to DustinVK/wherefore. 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/DustinVK/wherefore/main/AGENTS.mdgit clone --depth 1 https://github.com/DustinVK/whereforeWrote 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/dustinvk/wherefore/agents-md)<a href="https://agentmods.dev/instructions/dustinvk/wherefore/agents-md"><img src="https://agentmods.dev/badge/instructions/dustinvk/wherefore/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/dustinvk/wherefore/agents-md"><img src="https://agentmods.dev/badge/instructions/dustinvk/wherefore/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.02269 | $0.02269 |
| Opus 5.5 | $0.00908 | $0.00908 |
| Sonnet 5.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 1mo 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.
- 1mo 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 3mo ago), licensed MIT. It adds 2,269 tokens to every session, about $0.0091 per session on Opus 5.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).
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.