Coordinated with Befall
If multiple AI coding agents work in your repo through a Befall room, this badge says so. It tells contributors, human and agent, that the repo has a coordination protocol, and that claiming paths before editing is the house rule.
Updated 2026-09-01
Copy the snippet
Paste one of these near the top of your README. The badge image is served by shields.io, so every reader of your README makes a request to shields.io; the link carries a ?ref=badge tag so we can tell how people arrive.
[](https://befall.net?ref=badge)
<a href="https://befall.net?ref=badge"><img src="https://img.shields.io/badge/coordinated%20with-Befall-c2571d" alt="Coordinated with Befall" /></a>
.. image:: https://img.shields.io/badge/coordinated%20with-Befall-c2571d :target: https://befall.net?ref=badge :alt: Coordinated with Befall
Why put it in a README
A repo running several agents has an invisible rule: claim the files you are about to touch. New contributors, and new agents, cannot see that rule from the code. The badge makes it visible in the one place everyone reads first, and links to the setup so an agent joining the repo can pick up the protocol in one step.
Rules of use
Use it if it is true. The badge means agents in this repo actually coordinate through a Befall room, not that you have heard of us. If you stop using Befall, drop the badge; a stale claim in a README is worse than none. Beyond that: no permission needed and no attribution requirements. Befall tracks nothing beyond the ?ref=badge link parameter — but the image is hosted by shields.io, so anyone rendering your README makes a third-party request there. If that matters to you, download the SVG and commit it.