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/uetzel/autoadhd/claude-mdgit clone --depth 1 https://github.com/uetzel/AutoADHDWhat 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.03826 | $0.03826 |
| Opus 5 | $0.01913 | $0.01913 |
| Sonnet 5 | $0.00765 | $0.00765 |
| Haiku 4.5 | $0.00383 | $0.00383 |
Grade A, and why
AutoADHD 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 3d 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
You are an AI agent operating inside an Obsidian vault. Git tracks every change. If something goes wrong, we revert.
WHAT YOU CAN DO
- Create, edit, and delete notes in any folder
- Add new Canon entries directly (people, events, concepts, decisions, projects, actions — or new types as needed)
- Update existing Canon entries with new information
- Create and maintain wikilinks between notes
- Evolve the structure: new types, new relationship patterns, new folders are fine
- Research external context for concepts/ideas and add with proper source attribution
- Write AI reflections and observations to Meta/AI-Reflections/
WHAT YOU MUST NOT DO
- Never edit content under
# Rawin any Inbox note. Raw transcripts are source evidence and are read-only. - Never delete Inbox notes that contain raw transcripts
- Never fabricate information. If you're unsure, say so.
SKILLS (just-in-time context)
Skills inject focused rules at the moment you need them, instead of relying on this file surviving a long conversation. They live in .claude/skills/ and are loaded on demand.
| Skill | When to load | What it contains |
|---|---|---|
vault-writer |
Creating or editing ANY vault note | Note format, frontmatter, emoji headings, provenance, wikilinks, folder map |
vault-extractor |
Processing an Inbox note into Canon entries | Full extraction checklist, action detection, reflection handling, duplicate detection, write-back rules |
For Cowork sessions: Skills load automatically when triggered by the task description.
For CLI/Codex agents: Agent scripts should tell the agent to read the relevant skill file at runtime (lean prompt pattern) rather than dumping rules into the CLI argument. Example: "Read .claude/skills/vault-writer/SKILL.md before creating any notes."
Token discipline: Skills replace the need to load this entire CLAUDE.md into every agent prompt. Load only what the task requires. The vault-writer skill (~200 lines) replaces the note format, emoji, provenance, and wikilink sections of this file (~150 lines) — but with fresher context at the point of action.
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.
- 3d ago First seen · 383 lines · 3,826 tokens per session scan A 8eadfbb13ee3
AutoADHD CLAUDE.md is an instructions file published in the GitHub repository uetzel/AutoADHD (22 stars, last pushed 4mo ago), licensed MIT. It adds 3,826 tokens to every session, about $0.0191 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
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.