SOURCE VERIFIED111 lines
radareorg
radare2
Strong location map, formatting rules, memory safety, and command guidance.
Read source at 1dfe427OPEN INDEX / 001UPDATED 2026-07-25
Stop guessing
what belongs in
AGENTS.md
Real instruction files from serious open-source repositories—indexed by stack, scope, and safety pattern. Every entry points to a fixed source commit.
AGENTS.mdREADME.mdpackage.json
01# Working agreement
02
03## Scope
04Read the nearest rules before editing.
05Keep changes inside the requested package.
06
07## Done means verified
08Run the narrow test while iterating.
09Run the full check before handoff.
10
11## Protect existing work
12Never discard user changes.
100VERIFIED
SOURCES
SOURCES
- 100
- fixed sources
- 8
- rule patterns
- 744.8K
- combined repo stars*
- 0
- invented examples
01 / SOURCE INDEX
See how real projects brief their agents.
Browse fixed snapshots, then read the original file in context. Star counts are discovery metadata captured on 2026-07-25, not a quality score.
Showing 12 of 100 verified sources
SOURCE VERIFIED44 lines
benchmark
A compact policy focused on disclosing and reviewing AI-assisted work.
Read source at ff954e9SOURCE VERIFIED153 lines
GitoxideLabs
gitoxide
Test-first practices, error handling, commit messages, and path rules.
Read source at 2fadbc7SOURCE VERIFIED348 lines
Replicate
cog
A detailed command index with language-specific conventions.
Read source at 4e62b8bSOURCE VERIFIED86 lines
loro-dev
loro
A short project snapshot with a context index and self-maintained instructions.
Read source at 6844fc7SOURCE VERIFIED98 lines
NextDNS
nextdns
Core principles, testing guidance, dependency checks, and a binary budget.
Read source at cd213c9SOURCE VERIFIED31 lines
Chartbrew
chartbrew
An unusually concise monorepo map with client/server workflow instructions.
Read source at 944afa1SOURCE VERIFIED21 lines
Datadog
stratus-red-team
Twenty-one lines that focus entirely on creating and testing attack techniques.
Read source at 52db2f8SOURCE VERIFIED66 lines
DeepFlow
deepflow
Clearly separates source-of-truth files from generated artifacts.
Read source at 61221a2SOURCE VERIFIED179 lines
GraphFrames
graphframes
Legacy-code guardrails and regression prevention across Spark versions.
Read source at 926e9d9SOURCE VERIFIED211 lines
Palo Alto Networks
docusaurus-openapi-docs
Contributor quick start, required checks, and release instructions.
Read source at d6b33f9SOURCE VERIFIED69 lines
obi1kenobi
cargo-semver-checks
A focused set of scripts for testing and linting proposed changes.
Read source at a3331d002 / REPEATED PATTERNS
The useful parts repeat.
Frequency is descriptive, not proof of effectiveness. These counts come only from the verified source index.
01
90/100 sources
Code style
Formatter ownership and repository-specific code conventions.
Explore this pattern02
88/100 sources
Testing
Exact test commands, useful test scope, and expectations for changed behavior.
Explore this pattern03
82/100 sources
Safety
Hard boundaries for destructive, sensitive, or irreversible work.
Explore this pattern04
79/100 sources
Documentation
Pointers to architecture, contribution, and operational context.
Explore this pattern05
78/100 sources
Verification
The evidence required before an agent can call work complete.
Explore this pattern06
71/100 sources
Scope
Directory boundaries, project maps, and rules for nested instruction files.
Explore this pattern07
69/100 sources
Git workflow
Commit, branch, pull-request, and worktree expectations.
Explore this pattern08
48/100 sources
Generated files
Generated or vendored files and the commands that own them.
Explore this pattern03 / STARTER BUILDER
Start from patterns, not cargo cults.
Generate a small working agreement, then adapt it to the repository in front of you. The builder never claims that one file fits every codebase.
# AGENTS.md
## Project map
- Read the nearest README and package manifest before editing.
- Keep changes inside the requested feature or package.
- A nested AGENTS.md overrides this file for its directory.
## Commands
- Install: `npm install`
- Test: `npm test`
- Build: `npm run build`
## Working rules
- Preserve the existing TypeScript and component conventions. Run the configured formatter.
- Prefer the smallest change that satisfies the request.
- Explain any assumption that changes behavior or scope.
## Completion gate
- Run the narrowest relevant tests while iterating.
- Before handoff, run `npm test` and `npm run build`.
- A passing command is evidence for that command only; report anything not verified.
## Safety
- Never discard or overwrite user changes.
- Ask before destructive operations, publishing, spending money, or changing production data.
## Generated files
- Do not edit generated output by hand.
- Find and run the owning generator, then review both source and generated diffs.
## Git
- Keep commits scoped to one logical change.
- Do not push, force-push, rebase shared work, or open a pull request unless requested.
The builder and its evidence are open source.View on GitHub
- 01Fixed evidence
Every entry links to a commit, not a floating claim.
- 02License visible
We index by default and preserve provenance.
- 03No popularity shortcut
Stars help discovery; they do not certify instruction quality.
- 04Corrections welcome
Source owners can update, clarify, or request removal.