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/vinilana/dotcontext/claude-mdgit clone --depth 1 https://github.com/vinilana/dotcontextWrote 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/vinilana/dotcontext/claude-md)<a href="https://agentmods.dev/instructions/vinilana/dotcontext/claude-md"><img src="https://agentmods.dev/badge/instructions/vinilana/dotcontext/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.00458 | $0.00458 |
| Opus 5 | $0.00229 | $0.00229 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
dotcontext 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 4d 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.
What it actually says
Dotcontext Repository Guide
This repository is the source for the dotcontext runtime and its operator/adaptor surfaces.
Current product shape:
cli -> harness <- mcp
<- integrations (host hooks / extensions)
Source of Truth
Start here:
README.mdfor product description and install guidance- dotcontext.dev (
docs/) for usage guidance ARCHITECTURE.mdfor runtime and boundary diagramsCHANGELOG.mdfor release notes
Working Boundaries
src/clicontains operator-facing exports and CLI-oriented services (sync, MCP install, hook install, admin)src/harnesscontains reusable runtime exports — domain rules, application services, and adapterssrc/mcpcontains the MCP transport boundary — server, gateway handlers, and schemassrc/integrationscontains host hook adapters for Claude Code, Codex CLI, and Pi
Do not move domain behavior into cli, mcp, or integrations if it belongs in harness. Integrations call the harness only — they never import cli or mcp.
Current Priorities
The repository now supports:
- durable harness sessions
- sensors and backpressure
- task contracts and handoffs
- policy documents and policy evaluation
- replay and failure datasets
- host hook install for Claude Code, Codex CLI, and Pi
- local packaging for
cli,harness,mcp,integrations, andpi
Validation Commands
npm run build
npm test -- --runInBand
npm run build:packages
npm run smoke:packages
Documentation Hygiene
When changing any of the following, keep docs in sync:
- product positioning
- MCP install behavior
- hook install behavior
- package boundaries
- workflow commands
- release/versioning guidance
At minimum, review:
README.mddocs/src/content/docs/(published at dotcontext.dev)ARCHITECTURE.mdCONTRIBUTING.mdCHANGELOG.md
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.
- 4d ago First seen · 69 lines · 458 tokens per session scan A 541f341cbac1
dotcontext CLAUDE.md is an instructions file published in the GitHub repository vinilana/dotcontext (564 stars, last pushed 1mo ago), licensed MIT. It adds 458 tokens to every session, about $0.0023 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.