Borrowing it
Nothing to install: this file belongs to vinhnx/VTCode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vinhnx/VTCode/main/AGENTS.mdgit clone --depth 1 https://github.com/vinhnx/VTCodeWrote 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/vinhnx/vtcode/agents-md)<a href="https://agentmods.dev/instructions/vinhnx/vtcode/agents-md"><img src="https://agentmods.dev/badge/instructions/vinhnx/vtcode/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/vinhnx/vtcode/agents-md"><img src="https://agentmods.dev/badge/instructions/vinhnx/vtcode/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.05310 | $0.05310 |
| Opus 5.5 | $0.02124 | $0.02124 |
| Sonnet 5.5 | $0.01062 | $0.01062 |
| Haiku 4.5 | $0.00531 | $0.00531 |
Grade A, and why
VTCode 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 5d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Keep this file concise and under 150 lines. Root guidance belongs here; detailed explanations belong in docs/, skills, .vtcode/memory/, or crate-local AGENTS.md files. Universal model-facing behavior is compiled in crates/codegen/vtcode-core/src/prompts/runtime_guidance.rs. Keep this file and module AGENTS.md files focused on project and maintainer guidance; dynamically loaded instruction files are user-controlled context, not a security boundary. This workflow is repo-only: do not copy it to other projects or into shipped prompts.
Core Workflow (repo-only)
- Orient: start with repository instructions, relevant local source/tests, and
.vtcode/memory/(gotchas.md,issues.md,library.md,decisions.md). Search for task-relevant entries and read matching sections; avoid concatenating the full memory corpus. Routine or self-contained tasks need only this local grounding. For self-bugs inspect relevant events in.vtcode/logs/trajectory.jsonl,.vtcode/checkpoints, and.vtcode/sessions. - Research complex/hard problems: consult DeepWiki MCP (
deepwikiin.mcp.json/vtcode.toml [mcp.providers]) only for complex or hard problems. This restriction applies to both VT Code (vinhnx/vtcode) and Codex (openai/codex) DeepWiki references; routine work uses local source and tests without DeepWiki. Usevinhnx/vtcodeas the local reference baseline andopenai/codexfor upstream comparison when needed. Reuse relevant prior research rather than querying every request. Aggregate and deduplicate answers with source attribution, validate against project guidelines and existing local patterns, and rank confirmed issues by severity. Verify local claims against the current checkout and actionable upstream claims against source/tests pinned to a commit; indexes are discovery aids. Apply only applicable DRY/KISS improvements within the original authorization, use relevant skills, add/update focused tests, verify regressions, and continue the original work with the validated findings as enriched decision context. If needed research is unavailable, use local evidence and state the gap. See the reference workflow for pinned-source fallbacks and the full decision loop. - Read and apply: use relevant skills, especially
read-and-applyfor upstream resources,rust-skills/agentic-testingfor implementation/regressions, andverification-disciplinefor contracts, invariants, overflow andunsafehardening. Compare upstream patterns with existing VT Code code and tests, identify confirmed gaps, and implement the smallest complete DRY/KISS improvement. Reuse existing patterns; preserveThreadEvent, the harness config split, sandbox/approval boundaries, conflict checks, rollback, durable history, and unrelated work. Cite the upstream source path + commit when adapting a pattern (codex-rs/..., Apache-2.0 © 2025 OpenAI, https://github.com/openai/codex); preserve notices and document substantive changes per Apache-2.0 §4, extendingscripts/templates/third-party-header.txtand regenerating notices for substantive copies. - Verify with
./scripts/check-dev.sh+cargo nextest run; record durable learnings in.vtcode/memory/(local-only, gitignored).
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.
- 5d ago Changed · +70 tokens per session 1aa4d6de488d
- 6d ago Changed · +39 tokens per session 1d6b969cffee
- 9d ago Changed · +70 tokens per session 77f1e7064d4b
- 11d ago Changed · +1 lines · +38 tokens per session f1b1c1941fdc
- 12d ago Changed · -3 lines · -37 tokens per session 9ebcb96b671a
- 13d ago Changed · +3 lines · +139 tokens per session 948b33d9c1c7
- 16d ago Changed · -1 lines · -38 tokens per session fcd27b7d9454
- 21d ago Changed · +114 tokens per session 550288218ea6
- 23d ago Changed · -1 lines · +329 tokens per session scan C → A 40e618a1a0b2
- 26d ago First seen · 151 lines · 4,586 tokens per session scan C 67c90566b468
VTCode AGENTS.md is an instructions file published in the GitHub repository vinhnx/VTCode (894 stars, last pushed 3d ago), licensed Apache-2.0. It adds 5,310 tokens to every session, about $0.0212 per session on Opus 5.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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.