Borrowing it
Nothing to install: this file belongs to Vironnimo/vbot. 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/Vironnimo/vbot/main/AGENTS.mdgit clone --depth 1 https://github.com/Vironnimo/vbotWrote 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/vironnimo/vbot/agents-md)<a href="https://agentmods.dev/instructions/vironnimo/vbot/agents-md"><img src="https://agentmods.dev/badge/instructions/vironnimo/vbot/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/vironnimo/vbot/agents-md"><img src="https://agentmods.dev/badge/instructions/vironnimo/vbot/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.02544 | $0.02544 |
| Opus 5.5 | $0.01018 | $0.01018 |
| Sonnet 5.5 | $0.00509 | $0.00509 |
| Haiku 4.5 | $0.00254 | $0.00254 |
Grade A, and why
vbot 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 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Load context for the task
At session start, read these core files completely unless their current contents are already in context. Load them once; re-read affected sections when they change:
.vorch/PROJECT.md- project context.vorch/GLOSSARY.md- project-specific terms
Before working in or discussing a domain, read its root map under .vorch/domain-maps/ (index in PROJECT.md), plus adjacent maps when ownership or contracts cross domains. Use them to locate owners, contracts, source, and tests. The task's read: list is a starting point; add a map only when the task reaches into its domain. Follow the root map's ## References only for supplementary files whose triggers match the task; do not preload a supplementary folder. Supplementary files never replace the root map or enter the Domain Maps index.
Before changing a domain map or supplementary file, read .vorch/workflows/domain-map-workflow.md up to ## Creating or restructuring a map unless its current contents are already in context; read the rest too when you create, split, merge, rename or restructure a map. Ordinary map reading does not require that workflow.
Interpret documentation
Distinguish explicit user requirements and engineering contracts from descriptions of current behavior, examples, and proposals. Follow applicable requirements and contracts; a documented implementation or past choice is not automatically a constraint on new work. Existing behavior and design may be revised within the user's requested scope without a documentation exception. When the user asks to rethink or rebuild a system, its documented design, invariants and earlier decisions about it are open for revision; say which ones you would keep and why. A recorded user requirement stays in force until the user agrees to drop it by name.
Source code establishes what is implemented, not what ought to be implemented. Verify behavior claims against source and relevant tests. Correct stale descriptions; when code conflicts with an explicit requirement or contract, address the discrepancy rather than rewriting the requirement to match the code. Keep observations, requirements, and proposed changes identifiable in the docs.
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 Changed · +62 tokens per session 588763b354d5
- 10d ago Changed · +32 tokens per session cf011df57d97
- 11d ago Changed · +84 tokens per session ca6fe7c3a766
- 13d ago Changed · +40 tokens per session b3a775e721b9
- 17d ago Changed · +1 lines · +72 tokens per session c83c043bbc8d
- 19d ago Changed · +27 tokens per session 6d63524b3f47
- 20d ago Changed · -26 lines · -508 tokens per session e0ece46c7e49
- 23d ago Changed · +2 lines · +130 tokens per session 8b87c543177d
- 26d ago Changed · +1 lines · +119 tokens per session ba8b22b2571b
- 27d ago First seen · 119 lines · 2,486 tokens per session scan A 6270f2e9fd9b
vbot AGENTS.md is an instructions file published in the GitHub repository Vironnimo/vbot (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,544 tokens to every session, about $0.0102 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-31.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.