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/copilot-instructionsgit 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.00030 | $0.00030 |
| Opus 5 | $0.00015 | $0.00015 |
| Sonnet 5 | $0.00006 | $0.00006 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
wherefore copilot-instructions.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 yesterday.
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.
What it actually says
This project's decision-log conventions are defined in AGENTS.md at the repo root. Follow it when reading or writing anything under the wherefore/ directory.
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.
- yesterday First seen · 3 lines · 30 tokens per session scan A fef74aa43dbb
wherefore copilot-instructions.md is an instructions file published in the GitHub repository DustinVK/wherefore (1 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session, about $0.0002 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.