Borrowing it
Nothing to install: this file belongs to burakgon/roamcode. 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/burakgon/roamcode/main/AGENTS.mdgit clone --depth 1 https://github.com/burakgon/roamcodeWrote 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/burakgon/roamcode/agents-md)<a href="https://agentmods.dev/instructions/burakgon/roamcode/agents-md"><img src="https://agentmods.dev/badge/instructions/burakgon/roamcode/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/burakgon/roamcode/agents-md"><img src="https://agentmods.dev/badge/instructions/burakgon/roamcode/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.01281 | $0.01281 |
| Opus 5.5 | $0.00512 | $0.00512 |
| Sonnet 5.5 | $0.00256 | $0.00256 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
roamcode 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository instructions for coding agents
These instructions apply to the entire repository. This is a public repository: write every file, commit, log, issue, release note, and command as if it will be visible to anyone on the internet.
Public-repository safety
- Never commit, print, paste, or request credentials, access tokens, cookies, private keys,
.npmrccontents, signing material, or authenticated URLs. Use the existing GitHub environments and trusted publishing. - Never add a maintainer's username, home directory, machine-specific absolute path, private hostname, tunnel URL, session identifier, or production log contents to the repository.
- Keep local service data, live sessions, and unrelated worktree changes intact. Do not clean, reset, or overwrite changes that are outside the requested task.
- Do not mutate or restart a developer's installed RoamCode service merely to test a change. A live install, manual migration, rollback, or restart requires an explicit user request. Use isolated tests and GitHub Actions for boot and package-install smoke tests.
Stable release and OTA contract
- A commit or push to
mainis not an update. Users discover updates only through stable, non-draft GitHub Releases. - Stable SemVer (
X.Y.Z) is the only release identity. The workspace, CLI, server, web package, npm artifacts, GitHub tag/release, release manifest, and Homebrew formula must agree on the exact version. - The stable release workflow must publish npm artifacts and the Homebrew formula before it creates the discoverable GitHub Release. Never manually reverse this order.
- OTA installs the exact npm version whose integrity is recorded in
roamcode-release.json; do not reintroduce commit-, branch-, or checkout-based update behavior. - Release descriptions are user-facing OTA data.
scripts/release-notes.mjsextracts them fromCHANGELOG.md, and the web client groups their Markdown bullets under headings such asAdded,Fixed, andChanged. Every release section must contain at least one accurate bullet so What's new is never empty. - Never reuse a published version for different package bytes. If a workflow fails, first determine which external artifacts exist; resume only when the workflow can prove any existing immutable npm artifacts match exactly.
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 First seen · 88 lines · 1,281 tokens per session scan A c3bacc8400ee
roamcode AGENTS.md is an instructions file published in the GitHub repository burakgon/roamcode (19 stars, last pushed 20d ago), licensed MIT. It adds 1,281 tokens to every session, about $0.0051 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.