Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/web3dev1337/gastown-gui/agents-mdgit clone --depth 1 https://github.com/web3dev1337/gastown-guiWhat 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 | $0.00102 | $0.00102 |
| Opus 5 | $0.00051 | $0.00051 |
| Sonnet 5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
gastown-gui 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 3d 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.
What it actually says
AGENTS.md
READ THE ENTIRE CLAUDE.md FILE BEFORE MAKING ANY CHANGES.
This file exists for AI tools that don't automatically read CLAUDE.md (Cursor, Aider, etc.).
All project documentation, architecture, commands, and patterns are in CLAUDE.md.
Additional Rule
- No god files/classes. If logic grows in
server.js(or any large file), extract it into dedicated modules underserver/by responsibility.
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.
- 3d ago First seen · 12 lines · 102 tokens per session scan A 050536e71442
gastown-gui AGENTS.md is an instructions file published in the GitHub repository web3dev1337/gastown-gui (87 stars, last pushed 4mo ago), licensed MIT. It adds 102 tokens to every session, about $0.0005 per session on Opus 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
nexent AGENTS.md
AGENTS.md instructions for ModelEngine-Group/nexent, covering agents, available skills, project overview, developer commands and backend (python 3.11).
optillm CLAUDE.md
Instructions for algorithmicsuperintelligence/optillm, covering claude.md, project overview, core architecture, main components and development commands.
thinkrail AGENTS.md
Instructions for JetBrains/thinkrail, covering thinkrail, module structure & boundaries (top-priority requirement), engine: pi only, in-process, architecture (three rings) and repo layout.
LeAgent AGENTS.md
Instructions for vixues/LeAgent, covering leagent development guidelines, project overview, architecture, execution topology (one kernel, many ingresses) and surface map (where things live).
grix AGENTS.md
Instructions for askie/grix, covering grix agent guide, repository boundaries, required workflows, shared agent configuration and cross-component contracts.
rn-dev-agent AGENTS.md
Instructions for Lykhoyda/rn-dev-agent, covering repository guide for agents, repository map, editing rules, architecture rules and supported node runtimes.