Goose is an open-source AI agent that runs on a computer as a desktop app, command-line tool, or API and can perform tasks beyond code completion. Developers and other users employ it for coding, research, writing, automation, and data analysis with different language-model providers and extensions. The catalogue add-ons define parts of its agent workflow and behavior.
Borrowing it
Nothing to install: this file belongs to aaif-goose/goose. 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/aaif-goose/goose/main/AGENTS.mdgit clone --depth 1 https://github.com/aaif-goose/gooseWrote 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/aaif-goose/goose/agents-md)<a href="https://agentmods.dev/instructions/aaif-goose/goose/agents-md"><img src="https://agentmods.dev/badge/instructions/aaif-goose/goose/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/aaif-goose/goose/agents-md"><img src="https://agentmods.dev/badge/instructions/aaif-goose/goose/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.01430 | $0.01430 |
| Opus 5.5 | $0.00572 | $0.00572 |
| Sonnet 5.5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
goose 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 12d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS Instructions
goose is an AI agent framework in Rust with CLI and Electron desktop interfaces.
Contribution Workflow
The issue is the source of truth for work intended for an upstream pull request. Track issue status on the Goose Issues board.
- Before implementing an issue for a pull request, confirm that it is on the board with Status Ready.
- Do not implement issues in Inbox, Needs info, or Accepted / design. Help resolve the issue discussion instead.
- Read the agreed design, constraints, non-goals, and verification plan before changing code.
- Keep the implementation within the issue's agreed scope.
- If implementation reveals a material design change, return to the issue before continuing.
- Every external pull request must link the Ready issue it implements and explain how the verification plan was performed.
- Structure new issues on the matching template in
.github/ISSUE_TEMPLATE/and set the issue type (e.g. Bug, Feature).gh issue createdoes not apply templates automatically.
Maintainer-directed work, urgent security fixes, release automation, and local or exploratory changes do not require a Ready issue.
MCP Server Directory
goose is retiring its project-specific MCP server directory in favor of the official MCP Registry and its server.json format.
- Do not add new third-party servers to
documentation/static/servers.json; these contributions are no longer accepted. - Direct server authors to publish to the official MCP Registry instead.
- Treat the existing goose directory as legacy data while registry-backed discovery and installation are implemented.
- Changes that maintain, migrate, or remove existing directory entries are allowed when they support the migration and are within an approved issue's scope.
See Discussion #10830 for the decision and migration direction.
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.
- 12d ago Changed · +1 lines · +25 tokens per session 6965989f2660
- 13d ago Changed · -6 lines · -98 tokens per session 859f43810e13
- 1mo ago Changed · +2 lines · +118 tokens per session 3c852fbffd75
- 1mo ago Changed · +11 lines · +155 tokens per session c6b08e61b25a
- 1mo ago First seen · 125 lines · 1,230 tokens per session scan A f894fb3d53e8
goose AGENTS.md is an instructions file published in the GitHub repository aaif-goose/goose (55,512 stars, last pushed today), licensed Apache-2.0. It adds 1,430 tokens to every session, about $0.0057 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.