Vanchor: Instructions file for Codex

AGENTS.md

Vanchor AGENTS.md is an instructions file for Codex, OpenCode from AlexAsplund/Vanchor. It costs 2,154 tokens per session, scanned A, original, MIT.

Project instructions for Vanchor-NG, a system that simulates and controls an autonomous boat through navigation, sensors, a web interface, and APIs.

In plain words
What is it for?
Understand the backend, simulation, frontend, REST and WebSocket APIs, and testing workflow before changing the boat-control software.
Why use it?
They direct coding agents to test control and navigation changes in a simulation and keep the project’s specialized documentation up to date.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is AlexAsplund/Vanchor's own configuration. It tells Codex and OpenCode how to work on Vanchor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Vanchor configures →

Reuse

Borrowing it

Nothing to install: this file belongs to AlexAsplund/Vanchor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AlexAsplund/Vanchor/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/AlexAsplund/Vanchor

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for Vanchor AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/alexasplund/vanchor/agents-md/github.svg)](https://agentmods.dev/instructions/alexasplund/vanchor/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/alexasplund/vanchor/agents-md"><img src="https://agentmods.dev/badge/instructions/alexasplund/vanchor/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.

agentmods 80×15 button for Vanchor AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/alexasplund/vanchor/agents-md"><img src="https://agentmods.dev/badge/instructions/alexasplund/vanchor/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,154 This file is loaded in full into every session.
When invoked 2,154 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.02154 $0.02154
Opus 5.5 $0.00862 $0.00862
Sonnet 5.5 $0.00431 $0.00431
Haiku 4.5 $0.00215 $0.00215

Measured 2mo ago against content hash bae93dc5db8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Vanchor 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 2mo 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 · 152 lines

How it starts

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

AGENTS.md — start here

You are an AI/LLM about to work on Vanchor-NG. Before editing anything:

1. Read the developer guide

docs/llms/README.md is the curated, LLM-oriented guide to the whole project. It orients you in ~5 minutes and links to per-area guides:

2. Golden rules

  • Simulate, don't theorise. Reproduce + measure control/nav changes in the harness (tests/harness.py) before claiming they work.
  • Keep new defaults a no-op so the full suite stays green.
  • Run the server from the repo root (the data dir is cwd-relative).
  • Front end has no build step; node --check is the only JS gate; the service worker is network-first (bump its version + SHELL list when you add/change shell assets).

3. 🔁 Keep docs/llms/* current — mandatory

Whenever you add, remove, rename, or change behaviour of code, update the matching docs/llms/* file in the same change, before considering the task done. A stale guide misleads the next agent. See the "Keeping these docs current" section in docs/llms/README.md.

4. Writing docs

For the human docs in docs/ (the docs/llms/* rule above still governs the LLM guide):

  • Concise and spacious. A shorter version with the same information is better. Prefer tables over prose lists. One idea per paragraph.
  • One home per topic. Don't duplicate across files — link instead. Adding or removing a doc means updating the index in docs/README.md.
  • Describe current reality, not history. roadmap.md is what's next; shipped work belongs in the CHANGELOG. When you implement a design/research doc, fold the still-useful bits into the living docs and delete the stale design doc — don't leave a "recommend X" doc once X ships. Never rewrite the CHANGELOG's dated entries (they're point-in-time).
  • No stale claims, no broken links. Update wording when behaviour changes; keep internal .md links valid.
  • docs/api/ is generated by make docs — don't hand-edit it.

Read the full file on GitHub · 152 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. 2mo ago First seen · 152 lines · 2,154 tokens per session scan A bae93dc5db8f

Subscribe to this mod's changes

Vanchor AGENTS.md is an instructions file published in the GitHub repository AlexAsplund/Vanchor (125 stars, last pushed 2mo ago), licensed MIT. It adds 2,154 tokens to every session, about $0.0086 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.

Related

Vanchor AGENTS.md compared with instructions from other repositories

Vanchor AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
Vanchor AGENTS.mdAlexAsplund/VanchorInstructions file1252mo agoMITA2,154Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot