Home / breadstick-crumbs / fanout · GitHub

llms.txtA

llms.txt from breadstick-crumbs/fanout is an llms.txt file: plain text a project publishes for AI models to read.

Install it, pinned
mdr add breadstick-crumbs/fanout/llms.txt@git:20261027.ae19466

Pins git:20261027.ae19466 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 14 of 14 checks passed
Kind
llms.txt file
Repository
breadstick-crumbs/fanout
Path
llms.txt
Versions recorded
3
Latest version
git:20261027.ae19466, committed Oct 27, 2026
First version recorded
Oct 25, 2026
Size
3,015 bytes
Repository stars
5
License
MIT

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# fanout

> fanout keeps several coding agents (Claude Code, Codex, or any CLI agent) on one git repo out of each other's way. For sessions you open yourself, with no setup: a new session is told what the others are doing, its task is claimed on its first edit, the same work described in other words is refused (a model check), and a session is told, with the diff, when another session's commit changes code it uses. For one job split across agents (`fanout run`): each agent works on its own branch and worktree and may only change the files it owns, shared interfaces are frozen, and every branch is merged on a scratch copy and tested before main, with each break sent back to the agent that caused it. No dependencies: Node 18+ and git. MIT licensed.

Use fanout when:
- you already run several agent sessions or worktrees on one repo: claims and notices switch on by themselves with two or more active, and `fanout` shows which ones are changing the same files
- a job is big enough to split across parallel agents and splits into parts with their own files
- several agents touch shared code, where a clean git merge can still break the build
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add breadstick-crumbs/fanout/llms.txt@sha256:7653b7b03ce32329

The line at the top of this page pins the label git:20261027.ae19466, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_lfyh3pomckdug4cn.svg)](https://markdownregistry.com/a/art_lfyh3pomckdug4cn)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Oct 25, 2026 and Oct 27, 2026, more than one a day.

versioncommittedcommitsizeaudit
git:20261027.ae19466 latest2026-10-27 ae19466 3,015 BA view · diff
git:20261026.f36f9db2026-10-26 f36f9db 2,871 BA view · diff
git:20261025.34b64b52026-10-25 34b64b5 2,174 BA view

Audit of the latest version

A  14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Size between 200 bytes and 200 KB (3015 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

breadstick-crumbs/fanout · 5 stars · license MIT · pushed 2026-11-08 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_lfyh3pomckdug4cn
GET https://markdownregistry.com/api/v1/resolve?ref=breadstick-crumbs/fanout/llms.txt
GET https://markdownregistry.com/api/v1/blob/7653b7b03ce3232988b8409a58df09c2984adc66482e13730b8967d67524899e

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: how to add an llms.txt file to a website · which agent file does what.

More from breadstick-crumbs/fanout

fanout SKILL.md skill
breadstick-crumbs/fanout · skills/fanout/SKILL.md · Use when the user wants to split a goal into parallel coding-agent sessions (Claude Code, Codex, or both) on git…
git:20261107.84373fe · audit A · 5 stars

Every file in breadstick-crumbs/fanout

Other files named llms.txt

llms.txt llms.txt file
tt-a1i/archify · llms.txt
git:20261031.afcf783 · audit A · 94,561 stars
llms.txt llms.txt file
garrytan/gbrain · llms.txt
git:20261104.dea361e · audit A · 31,587 stars
llms.txt llms.txt file
othmanadi/planning-with-files · llms.txt
git:20260917.2fbbd77 · audit A · 27,905 stars
llms.txt llms.txt file
tw93/kami · llms.txt
git:20261009.3d11cf5 · audit B · 12,282 stars
llms.txt llms.txt file
tw93/waza · llms.txt
git:20260907.2ae9e48 · audit A · 7,521 stars
llms.txt llms.txt file
deanchensj/jiangshan-map · llms.txt
git:20261104.0708131 · audit A · 4,690 stars
llms.txt llms.txt file
nteract/semiotic · llms.txt
git:20261006.a110d98 · audit A · 2,717 stars
llms.txt llms.txt file
ethanyoq/ai-novel-writer · llms.txt
git:20261018.88fb1ad · audit A · 2,388 stars

Browse by kind, by grade A, or by owner.