agentleFS
Sign inStart free
felipelobomotta-blipfelipelobomotta-blip/book-genesis-v4/AGENTS.md

book-genesis-v4

AGENTS.md159 starsChanged 19 days agoMITView on GitHub

This repository contains Book Genesis, a set of Agent Skills for writing complete books inside an agent host. When writing from this recovery checkout, read skills/book-genesis/SKILL.md directly and resolve references/... paths from skills/book-genesis/. A global installed skill may be a different release; do not silently use it to validate this build. For a project-local installation, run the installer's verify-install against this checkout before starting and record the installed version and file hashes in the run report.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. felipelobomotta-blip/book-genesis-studio★ 159100% 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 31,542 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 repository4 other files it gives its agents.

The file

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

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Start with skills/book-genesis/references/pipeline/host-contract.md, then references/prompts/orchestrator.md.

    line 9
  2. Very specific:

    Write the book in a folder outside this repository, or under books/, which git ignores.

    line 10
  3. Distinctive:

    Never skip Phase 4, and never score before it.

    line 11
  4. Distinctive:

    Write the book and every message to the author in the book's language.

    line 13
  5. Very specific:

    Before committing, run python runner/installer.py verify-suite and python -m unittest discover -s tests -v.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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

Agent instructions

This repository contains Book Genesis, a set of Agent Skills for writing complete books inside an agent host.

Writing a book from this checkout

When writing from this recovery checkout, read skills/book-genesis/SKILL.md directly and resolve references/... paths from skills/book-genesis/. A global installed skill may be a different release; do not silently use it to validate this build. For a project-local installation, run the installer's verify-install against this checkout before starting and record the installed version and file hashes in the run report.

  • Start with skills/book-genesis/references/pipeline/host-contract.md, then references/prompts/orchestrator.md.
  • Write the book in a folder outside this repository, or under books/, which git ignores.
  • Never skip Phase 4, and never score before it.
  • Critics never see targets or earlier scores; the writer never sees the rubric.
  • Write the book and every message to the author in the book's language.

Working on the repository

  • Product instructions live in skills/book-genesis/. The three standalone skills live beside it and must not depend on it.
  • agents/ is generated. Edit skills/book-genesis/references/roles/, then run python runner/installer.py generate-agents.
  • Before committing, run python runner/installer.py verify-suite and python -m unittest discover -s tests -v.
  • See CONTRIBUTING.md for the rules and docs/architecture.md for the design.

Download now (ZIP)

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