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/oshadha345/contxt-box/agents-mdgit clone --depth 1 https://github.com/Oshadha345/contxt-boxWrote 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/oshadha345/contxt-box/agents-md)<a href="https://agentmods.dev/instructions/oshadha345/contxt-box/agents-md"><img src="https://agentmods.dev/badge/instructions/oshadha345/contxt-box/agents-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.00762 | $0.00762 |
| Opus 5 | $0.00381 | $0.00381 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
contxt-box 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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
ConTXT BOX agents follow a strict Ponytail plus gstack style: minimal, structured, scoped, and reliable. The product goal is an external context box that connects any local folder to coding assistants through CLI and MCP.
Non-Negotiable Scope
- Core heavy extraction has exactly two supported engines: MarkItDown and Docling.
- Do not add fallback chains across OCR, audio, video, Whisper, FFmpeg, Chunkr, or vision APIs unless the product scope is explicitly changed.
- Indexing must stay lazy. Do not open or parse heavy documents/images during
indexor watchdog updates. - Heavy extraction happens only through
extract-mediaor MCPget_file(path, depth="full"). - Never overwrite user files. Store generated context only under
.contextbox/.
Index Contract
Every indexed file must include:
rel_pathfilenamefolder_pathmtimesizefile_typeneighborsparent_folder_summarylast_indexedcontext_summary
Cheap context_summary must be based on filename, folder, and neighbors only. It should be 1-2 concise sentences and avoid wild speculation.
Configuration Contract
initmust create.contextbox/config.tomlif it is missing.- Runtime behavior must load
.contextbox/config.tomlthroughAppConfig.for_root. - Configurable settings include extraction engine, ignore directories, priority folders, max neighbors, inline byte limit, large file limit, watchdog debounce, and auto-watch.
- Do not add hidden behavior that bypasses the workspace config.
Folder And Neighbor Rules
- Every folder gets a lightweight summary based on its name and top-level files.
- Every file records up to 10 sibling files.
- File summaries should use 5-7 nearby files as context cues.
- Prioritize special folders in indexing order:
codebases/,research/,specs/,decisions/,assets/images/.
Extraction Contract
- Cache sidecars at
.contextbox/history/media/<sanitized_path>.context.md. - After extraction, update
index.jsonwithextracted_at,context_ref,extraction_method,extraction_status,extraction_warnings, andextraction_duration_seconds. - Capture engine warnings and noisy stdout/stderr as structured audit metadata.
- Large files over 50 MB get metadata-only sidecars unless explicit chunked extraction is implemented later.
- The configured engine is strict. If Docling is selected and fails, report the failure. Do not silently switch to MarkItDown.
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 · 82 lines · 762 tokens per session scan A ce51c5c9a7d7
contxt-box AGENTS.md is an instructions file published in the GitHub repository Oshadha345/contxt-box (0 stars, last pushed 2mo ago), licensed MIT. It adds 762 tokens to every session, about $0.0038 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-09-01.
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.