Borrowing it
Nothing to install: this file belongs to ballast-ai/token-station. 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/ballast-ai/token-station/main/AGENTS.mdgit clone --depth 1 https://github.com/ballast-ai/token-stationWrote 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/ballast-ai/token-station/agents-md)<a href="https://agentmods.dev/instructions/ballast-ai/token-station/agents-md"><img src="https://agentmods.dev/badge/instructions/ballast-ai/token-station/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/ballast-ai/token-station/agents-md"><img src="https://agentmods.dev/badge/instructions/ballast-ai/token-station/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.03278 | $0.03278 |
| Opus 5.5 | $0.01311 | $0.01311 |
| Sonnet 5.5 | $0.00656 | $0.00656 |
| Haiku 4.5 | $0.00328 | $0.00328 |
Grade A, and why
token-station 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 1mo 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Token Station Engineering Rules
Use English by default
Use English for new and modified technical content. This rule applies to code comments, documentation, design records, test names, commit messages, pull requests, release notes, and contributor instructions.
Use ASCII English words for technical-document filenames. Locale suffixes such as zh-CN are allowed,
but localized words are not.
Keep commands, paths, protocol fields, API names, and code identifiers unchanged. Keep required localized user-interface text in its target language. You can quote an error or log entry in its original language.
If a document must contain English and Simplified Chinese, put the complete English text first. Put the complete Simplified Chinese text after it.
Write commit messages in English. Use a short imperative subject. Describe one logical change in each commit.
Commit directly to main
Work on the main branch. Commit authorized changes directly to main.
Do not create feature, topic, release, or migration branches unless the user explicitly requests one. Do not create a pull request unless the user explicitly requests one.
After you complete a feature or task, commit all authorized changes locally. Use an English commit message.
Before each commit, verify that the current branch is main. Stage only the files authorized for that
commit. Keep unrelated working-tree changes unstaged.
Use Simplified Technical English
Use strict Simplified Technical English for procedures, runbooks, safety warnings, and error messages.
- Put one instruction in each sentence.
- Put the condition before the action.
- Use the imperative form for instructions.
- Keep an instruction at 20 words or fewer when practical.
- Keep a descriptive sentence at 25 words or fewer when practical.
- Use active voice when the actor is known.
- Do not use contractions or semicolons.
- Use one stable name for one thing.
- Prefer short and common words.
Use STE-flavored English for READMEs, design documents, pull requests, release notes, and general technical explanations. Keep the text direct and natural. Remove filler, marketing claims, and unnecessary abstract terms.
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.
- 1mo ago Changed · +14 tokens per session 09ac0f1a0624
- 1mo ago Changed · +16 tokens per session b82dcf688e6f
- 1mo ago Changed · +14 tokens per session 55af54182e1c
- 1mo ago Changed · +17 lines · +172 tokens per session 7319bd62742c
- 1mo ago First seen · 288 lines · 3,062 tokens per session scan A d939021874b3
token-station AGENTS.md is an instructions file published in the GitHub repository ballast-ai/token-station (9 stars, last pushed 3d ago), licensed Apache-2.0. It adds 3,278 tokens to every session, about $0.0131 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).
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.