agentmods.dev

dotcontext AGENTS.md

Repository instructions for dotcontext, a project that provides one runtime through a command-line interface, an agent harness, an MCP connection, and integrations with host tools. It explains the intended role of each part and where changes belong.

In plain words
What is it for?
Use it when changing dotcontext’s command-line interface, reusable runtime, MCP request handling, or integrations with tools such as Claude Code, Codex CLI, and Pi.
Why use it?
It helps coding agents understand the project structure and avoid putting logic in the wrong layer. It also points them to the repository references and expected validation steps.

Instructions file for CodexOpenCode

561 1mo ago A scan 555 tokens original MIT
View the source file vinilana/dotcontext
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/vinilana/dotcontext/agents-md
Clone the repo
git clone --depth 1 https://github.com/vinilana/dotcontext

Made for: Codex, OpenCode.

Per session 555 This file is loaded in full into every session.
When invoked 555 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.00555 $0.00555
Opus 5 $0.00278 $0.00278
Sonnet 5 $0.00111 $0.00111
Haiku 4.5 $0.00056 $0.00056

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

Security

Grade A, and why

dotcontext AGENTS.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.

AGENTS.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dotcontext Agent Instructions

This repository exposes one runtime through four surfaces:

cli -> harness <- mcp
              <- integrations (host hooks / extensions)

Agents working in this repo should preserve that separation.

Architectural Intent

  • cli is the operator interface
  • harness is the reusable execution runtime
  • mcp is the transport adapter for AI tools
  • integrations is the host hook and extension layer (Claude Code, Codex CLI, Pi)

If a change affects reusable execution logic, prefer src/harness/application. If a change affects reusable domain rules, prefer src/harness/domain. If a change affects protocol shape or request handling, prefer src/mcp/gateway. If a change affects user-facing commands or installation flows, prefer src/cli. If a change affects host event mapping or hook templates, prefer src/integrations. Do not add new code under src/services; that directory is not part of the target architecture.

Repository References

  • README.md explains what dotcontext is and why it exists
  • dotcontext.dev (source in docs/) explains how to use it
  • ARCHITECTURE.md explains how the harness works
  • CONTRIBUTING.md explains contributor workflow
  • CHANGELOG.md tracks release-facing changes

Expected Validation

For code changes:

npm run build
npm test -- --runInBand

For packaging or release-surface changes:

npm run build:packages
npm run smoke:packages

MCP Install Changes

If you touch mcp:install, keep these aligned:

  • src/cli/services/mcpInstallService.ts
  • src/cli/services/mcpInstallService.test.ts
  • README.md
  • docs/src/content/docs/ (published at dotcontext.dev)
  • CHANGELOG.md

Documentation must reflect the actual config written by the installer.

Hook Install Changes

If you touch hook install, keep these aligned:

  • src/cli/services/hookInstallService.ts
  • src/cli/services/hookDispatchService.ts
  • src/cli/services/__tests__/hookInstallService.test.ts
  • src/integrations/claude-code/, src/integrations/codex/, src/integrations/pi-dev/
  • README.md
  • docs/src/content/docs/ (installation and hooks guides)
  • CHANGELOG.md

Read the full file on GitHub · 75 lines

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 · 75 lines · 555 tokens per session scan A 49bc426d9ba4

Subscribe to this mod's changes

dotcontext AGENTS.md is an instructions file published in the GitHub repository vinilana/dotcontext (561 stars, last pushed 1mo ago), licensed MIT. It adds 555 tokens to every session, about $0.0028 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.

Related

Other instructions, from other repositories

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

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

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

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

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

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