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/jstxn/agentdir/claude-mdgit clone --depth 1 https://github.com/jstxn/agentdirWrote 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/jstxn/agentdir/claude-md)<a href="https://agentmods.dev/instructions/jstxn/agentdir/claude-md"><img src="https://agentmods.dev/badge/instructions/jstxn/agentdir/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.00613 | $0.00613 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
agentdir 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.
This is a copy
91% identical to agentdir copilot-instructions.md — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
AgentDir for Claude Code
AgentDir is agent-owned background instrumentation for this repository. The engineer installs or adopts it once; agents operate it during normal work.
- Before starting work in an unfamiliar checkout, run
agentdir root --require --quiet. Exit 0 means an initialized local or shared worktree store is ready; do not decide whether AgentDir is set up from the presence of.agentdirin this checkout. - If the probe exits 3, run
agentdir adopt --if-needed --gitignore user. If hook installation is blocked in a restricted linked worktree, rerun it with--no-hooks. - Then start non-trivial coding work yourself with
agentdir work start "<subsystem: distinctive behavior or constraint>". Keep the title concise but retrieval-specific: name the subsystem plus a distinctive behavior or constraint, preserving request terms likely to match prior work. - Read the printed context briefing, treat excerpts as previews, and prefer the printed
agentdir work context --pack <pack-id> --expand <number>command before using a source when implementation details, prior patterns, or exact evidence matter. Then close the review once: repeat--usein that command for every useful numbered source (agentdir work context --use <number> [--use <number> ...] --reason "<how they help>"), or runagentdir work context --none-relevant --reason "<why>". Use--skip --reason "<why>"only when review is impossible; no decision is needed when no sources are presented. Re-open lost output withagentdir work context --show. - Wrap evidence-bearing commands with
agentdir run -- <command>. - Evidence includes tests, lint, typecheck, builds, doctor checks, release checks, reproduced failures, and diagnostics used in final claims.
- Do not wrap routine exploration such as
rg,sed,nl,cat,ls,find, or quick read-onlygit status. - Use
agentdir evidence --briefandagentdir timelineto skim what happened. - Record each verification you will rely on with
agentdir claim <family> --passed|--failed, e.g.agentdir claim test --passed. Families: test, lint, typecheck, build, doctor, release. - Claim what the evidence shows, including failures.
agentdir audit claimscompares recorded claims against evidence, so a claim that overstates a result is reported as contradicted. - Re-recording a family replaces its earlier claim; withdraw one made in error with
agentdir claim <family> --retract. - Use
agentdir report final --format jsonoragentdir work finish --json --brieffor the agent handoff object before final claims when practical. - Do not record secrets, private keys, raw environment dumps, or credential-bearing command output.
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 · 21 lines · 613 tokens per session scan A eca70a38137d
agentdir CLAUDE.md is an instructions file published in the GitHub repository jstxn/agentdir (21 stars, last pushed 12d ago), licensed MIT. It adds 613 tokens to every session, about $0.0031 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to agentdir copilot-instructions.md, differing in 6 lines, and is treated as a copy.
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.