hoa / ibo2024
AGENTS.md15 starsChanged 41 days agoApache-2.0View on GitHub
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,439 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.
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 4
Treat only the two official English IBO 2024 PDFs in source/ as authoritative.
- Distinctive: line 5
Write natural-language biology solutions in Markdown.
- Distinctive: line 6
Keep prose clear and complete rather than artificially terse.
- Distinctive: line 9
Do not modify another worker's problem file.
- Very specific: line 10
Use two-digit filenames: q01.md through q50.md.
- Distinctive: line 12
Do not copy the official explanation verbatim.
≈ “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.
Files
IBO 2024 solution project instructions
- Work entirely offline. Do not use web search, browsers, network tools, remote APIs, or external downloads.
- Treat only the two official English IBO 2024 PDFs in
source/as authoritative. Each PDF contains the official answer and explanation section after the question section. - Write natural-language biology solutions in Markdown. Do not use Lean or formal-proof syntax.
- Keep prose clear and complete rather than artificially terse. Explain every statement A-D, including why false statements fail.
- Preserve the official truth pattern exactly. If your independent reasoning appears to conflict with the official key, state the issue in the problem file instead of silently changing the key.
- One solver worker owns exactly one independent exam task and writes exactly one file under
solutions/part-a/orsolutions/part-b/. - Do not modify another worker's problem file.
- Use two-digit filenames:
q01.mdthroughq50.md. - Each problem file must contain: problem/topic title, official answer pattern, and separate natural-language reasoning for A, B, C, and D.
- Do not copy the official explanation verbatim. Paraphrase it and fill in any reasoning needed to make it understandable.
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
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.

