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 commands/wbern/agent-instructions/gastown-setupgit clone --depth 1 https://github.com/wbern/agent-instructionsWhat 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.00025 | $0.01486 |
| Opus 5 | $0.00013 | $0.00743 |
| Sonnet 5 | $0.00005 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
gastown-setup 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Guidelines
Output Style
- Never explicitly mention TDD in code, comments, commits, PRs, or issues
- Write natural, descriptive code without meta-commentary about the development process
- The code should speak for itself - TDD is the process, not the product
Beads is available for task tracking. Use mcp__beads__* tools to manage issues (the user interacts via bd commands).
Plan File Restriction
NEVER create, read, or update plan.md files. Claude Code's internal planning files are disabled for this project. Use other methods to track implementation progress (e.g., comments, todo lists, or external tools).
Gas Town Setup
Bootstrap a new Gas Town installation — the multi-agent workspace from Steve Yegge (overview post).
This command leans on the upstream Gas Town docs rather than duplicating install steps that will drift. Your job is to walk the user through the decision points and hand off to the canonical instructions at the right time.
Phase 0: Prerequisite check
Verify the environment before suggesting anything:
| Check | Pass condition |
|---|---|
gt binary present |
command -v gt succeeds |
tmux present |
command -v tmux succeeds |
~/gt/ absent or empty |
First-time install only — don't clobber an existing town |
If ~/gt/ already exists and contains a settings/ or mayor/ dir, stop.
Show the user gt status and let them decide whether to repair, extend, or
nuke before reinstalling. Do not proceed past this point automatically.
If gt is missing, point the user at the install instructions in
gastown/README and exit.
Phase 1: Ask the user which flavor they want
Use AskUserQuestion:
Question: "Which Gas Town flavor do you want to bootstrap?" (header: "Flavor")
Options:
- Default (autonomous) — "Out-of-the-box Gas Town with full autonomous patrols. Higher token burn, more emergent behavior."
- Manual mode (me-and-my-crew preset) — "Apply the wbern/gastown-me-and-my-crew preset: disables autonomous patrols, keeps crew workers only. Lower token burn, you drive the work."
- Skip preset for now — "Just install default Gas Town. I can apply a preset later by visiting the preset repo."
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 · 154 lines · 25 tokens per session scan A d150e1c873c2
gastown-setup is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,486 once invoked, about $0.0001 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 commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
thread
Manage conversation threads (create, switch, update, delete, show).
handoff
Generate or load a session handoff. Usage: /handoff [create|resume].