agentmods.dev

ai-context CLAUDE.md

A project instruction file for Claude Code that imports shared ai-context rules and adds Claude-specific guidance. It covers planning, saved session context, and permission settings.

In plain words
What is it for?
Use it to guide multi-file plans, preserve session notes, restore context after compaction, and control how setup or maintenance commands edit files.
Why use it?
It lets Claude Code use the same project knowledge as other assistants and resume work after a context reset.

Instructions file

11 3mo ago A scan 266 tokens original MIT
View the source file dkothule/ai-context
Install

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.

agentmods
npx agentmods add instructions/dkothule/ai-context/claude-md
Clone the repo
git clone --depth 1 https://github.com/dkothule/ai-context
Per session 266 This file is loaded in full into every session.
When invoked 266 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00266 $0.00266
Opus 5 $0.00133 $0.00133
Sonnet 5 $0.00053 $0.00053
Haiku 4.5 $0.00027 $0.00027

Measured 2d ago against content hash 2fe1d6c2d985, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ai-context 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 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.

CLAUDE.md · 10 lines

What it actually says

@AGENTS.md

Claude Code

Claude Code reads CLAUDE.md (not AGENTS.md) — the @AGENTS.md import above pulls in the shared adapter so both tools use one source of truth. Claude-specific notes only below.

  • Plan mode: use /plan before multi-file refactors or architectural changes. Once approved, immediately write the plan to .ai-context/plans/YYYY-MM-DD-<topic>.md before beginning any implementation.
  • Compaction: a PreCompact hook autosaves the working transcript to .ai-context/sessions/YYYY-MM-DD-HHMM-precompact-autosave.md before every compaction (manual /compact or auto) so context is never lost. A SessionStart(compact) hook then reminds the fresh session via injected context — review the autosave, curate it into a proper session log, record the autosave filename as source_autosave, copy its local_transcript_ref if present, then delete the autosave.
  • Permissions: ai-context setup/compact/check-drift run with --permission-mode acceptEdits by default. Override via --permission-mode <mode> if you need stricter/looser permissions.
Changes

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.

  1. 2d ago First seen · 10 lines · 266 tokens per session scan A 2fe1d6c2d985

Subscribe to this mod's changes

ai-context CLAUDE.md is an instructions file published in the GitHub repository dkothule/ai-context (11 stars, last pushed 3mo ago), licensed MIT. It adds 266 tokens to every session, about $0.0013 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.

PlanningProductivity
Related

Other instructions, from other repositories

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.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens