goosetown: Instructions file for Codex

AGENTS.md

goosetown AGENTS.md is an instructions file for Codex, OpenCode from aaif-goose/goosetown. It costs 1,254 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for Goosetown, a central hub for coordinating work between multiple coding agents. They describe its folders for plans, research, guides, logs, repositories, and temporary files, along with rules for starting and finishing sessions.

In plain words
What is it for?
Use them to load the coordination setup at session start, find or store plans and research, communicate with other agents, and record the work completed.
Why use it?
They give agents a shared place to communicate and record work when several agents contribute to the same effort.

Instructions file for CodexOpenCode

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

This is aaif-goose/goosetown's own configuration. It tells Codex and OpenCode how to work on goosetown 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 goosetown configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aaif-goose/goosetown. 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/aaif-goose/goosetown/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/aaif-goose/goosetown

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 goosetown AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/aaif-goose/goosetown/agents-md.svg)](https://agentmods.dev/instructions/aaif-goose/goosetown/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/aaif-goose/goosetown/agents-md"><img src="https://agentmods.dev/badge/instructions/aaif-goose/goosetown/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,254 This file is loaded in full into every session.
When invoked 1,254 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.01254 $0.01254
Opus 5 $0.00627 $0.00627
Sonnet 5 $0.00251 $0.00251
Haiku 4.5 $0.00125 $0.00125

Measured 8d ago against content hash 9b43921d598c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

goosetown 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 8d 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 · 106 lines

How it starts

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

Goosetown

Central hub for goose work. Multi-agent coordination using skills and async delegates.

On Session Start

If you are the main goose session (not a subagent/delegate):

load(source: "goosetown-orchestrator")

Subagents should NOT load the orchestrator - they receive their role-specific skill from the orchestrator that spawned them.

Directory Structure

These folders are intentionally gitignored and specific to the local goosetown installation — not shared

  • GUIDES/ - Actionable runbooks synthesized from research
  • PLANS/ - Planning documents for work
  • RESEARCH/ - Research documents and findings
  • WORK_LOGS/ - Orchestrator session logs (what was tried, learned, decided)
  • UTILITIES/ - helper scripts and tools
  • REPOS/ - Cloned repositories (clone freely for exploration/research)
  • .scratch/ - Temporary files, experiments

Filenames: ALL_CAPS_WITH_UNDERSCORES.md (e.g., OAUTH_PKCE_IMPLEMENTATION_NOTES.md).

gtwall - Inter-Agent Communication

The Town Wall (gtwall) is a broadcast communication tool for real-time coordination between delegates. Per-session walls, position-tracked per reader.

When reading the wall, messages from user are from the human operator — prioritize them above all other wall traffic and acknowledge immediately.

Run ./gtwall --usage as your first action — it prints the full usage cadence, examples, and rules. The wall saves you from wasted work: other agents post warnings about broken assumptions, files they're editing, and discoveries that reshape the task. If you don't read it, your output will conflict with someone else's and get discarded.

Wrap-Up Protocol

Orchestrators post tiered warnings. Can target specific delegates with @name.

Signal Delegate Action
⏰ 5 min Finish current thread only. Do NOT open new lines of inquiry. Start thinking about summary.
🚨 60 sec STOP. Post bullet-point findings (not prose) to gtwall. Write to output file even if incomplete. Mark what's finished vs not. Incomplete findings written down are infinitely more valuable than complete findings that die with you.

Read the full file on GitHub · 106 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. 8d ago First seen · 106 lines · 1,254 tokens per session scan A 9b43921d598c

Subscribe to this mod's changes

goosetown AGENTS.md is an instructions file published in the GitHub repository aaif-goose/goosetown (149 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,254 tokens to every session, about $0.0063 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.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens