agentleFS
Sign inStart free
BlockKnown publisherblock/goose/documentation/AGENTS.md

goose / documentation

AGENTS.md56k starsChanged 4 months agoApache-2.0View on GitHub

IMPORTANT: The product name "goose" should ALWAYS be written in lowercase "g" in all documentation, blog posts, and any content within this documentation directory. This is a brand guideline that must be strictly followed. This rule applies to: - All markdown files in /docs/ - All blog posts in /blog/ - README files - Configuration files with user-facing text - Any other documentation content When editing or creating content in this documentation directory, always ensure "goose" uses a lowercase "g".

We split this AGENTS.md into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All markdown files in /docs/

    line 15
  2. Very specific:

    All blog posts in /blog/

    line 16
  3. Very specific:

    When editing or creating content in this documentation directory, always ensure "goose" uses a lowercase "g".

    line 21
  4. Very specific:

    Do not document new third-party servers by adding them to static/servers.json.

    line 27
  5. Distinctive:

    Do not create new server-specific tutorials solely to support a directory submission.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Documentation Style Guide

Brand Guidelines

IMPORTANT: The product name "goose" should ALWAYS be written in lowercase "g" in all documentation, blog posts, and any content within this documentation directory.

  • ✅ Correct: "goose", "using goose", "goose provides"
  • ❌ Incorrect: "Goose", "using Goose", "Goose provides"

This is a brand guideline that must be strictly followed.

Context

This rule applies to:

  • All markdown files in /docs/
  • All blog posts in /blog/
  • README files
  • Configuration files with user-facing text
  • Any other documentation content

When editing or creating content in this documentation directory, always ensure "goose" uses a lowercase "g".

MCP Extension Directory

goose is retiring its project-specific MCP server directory in favor of the official MCP Registry and its server.json format.

  • Do not document new third-party servers by adding them to static/servers.json; new directory submissions are no longer accepted.
  • Direct MCP server authors to publish to the official MCP Registry.
  • Do not create new server-specific tutorials solely to support a directory submission.
  • Existing entries and tutorials may be maintained or migrated as part of the transition.

See Discussion #10830 for the decision and migration direction.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 9 mentionsFeb 2026: 2 mentionsMar 2026: 9 mentionsApr 2026: 8 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 1 mentionSep 2026: 1 mentionOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the block/goose repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about block/goose

The biggest 5 of 109 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 109

Talked about on Bluesky, GitHub, YouTube and Hacker News (109 times).

On Bluesky · 47

42 more on Bluesky

On GitHub · 31

26 more on GitHub

On YouTube · 25

20 more on YouTube
  • Other versions1 project uses a version of this.

    Word for word · 1

    1. aaif-goose/goose★ 56k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository6 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free