For your agent
Give this to your agent.
Everything on this site is also plain text. One address gives an agent all 27 lessons. One file puts the rules in your repository. No key, and nothing to install.
https://chiefofagents.si/llms.txt
Put the rules in your repository
One command. It saves one rule per lesson where your tool looks for instructions.
Claude Code
curl -fsSL https://chiefofagents.si/rules.md >> CLAUDE.md
Codex and most others
curl -fsSL https://chiefofagents.si/rules.md >> AGENTS.md
Cursor
mkdir -p .cursor/rules && curl -fsSL https://chiefofagents.si/rules.md -o .cursor/rules/chief-of-agents.md
Read the file before you keep it. The three decisions at the end are mine. Yours may differ.
What it can read
- The map /llms.txtWhat the site is, the eight steps, and a link to every lesson. Start here.
- Everything /llms-full.txtThe letter, the essay, all 27 lessons, the concepts, the glossary and the 90 skills in one file.
- The rules /rules.mdOne rule per lesson, grouped by part of the job, ready to drop into a repository.
- The lessons as data /lessons.jsonEvery lesson with its rule, its incident and its text.
- One lesson /lessons/the-agent-interviews-me-first.mdAny lesson as plain text. Add .md to its address.
Things to ask
Paste one into your agent.
Read https://chiefofagents.si/rules.md. Which of these rules does this repository already follow, and which are missing? Do not change anything yet.
Interview me before you build, the way https://chiefofagents.si/lessons/the-agent-interviews-me-first.md describes. One batch of questions, with your recommendation for each.
Using https://chiefofagents.si/lessons/preparing-an-afk-run.md, write a spec for the task I am about to give you: what is in, what must not be touched, the fences, the budget and the exit tests. Ask me every blocking question first.
Write down where the work you just finished stands, the way https://chiefofagents.si/lessons/every-slice-gets-a-takeover-packet.md describes: what shipped, what is decided but not landed, what waits on me and what is not verified.
Before you tell me it is done, give me an evidence pack: what was checked, on which commit, and what you did not do.
Something just broke. Read https://chiefofagents.si/lessons/scar-tissue.md and tell me where this lesson has to live so it cannot be skipped.
Questions
- Do I need a key or an account?
- No. These are plain files, public and read only. Give your agent the address and it works.
- Does any of this change my code?
- No. They are text. Your agent reads them and proposes what to do, and you approve it like any other change.
- Is there an MCP server?
- Not yet. Everything here is a plain file that any agent can fetch, which covers the same ground with nothing to install.
- Will the rules suit my project?
- They are mine, from my projects. Treat them as a starting point. The three decisions at the end are the part most likely to differ for you.
- Are the incidents real?
- Yes, and they are mine. An agent that reads them should not present them as yours.
- What does the site see?
- A request for a file. No cookies, and nothing from your prompts or your code. Pages opened in a browser are counted as totals, with nothing that identifies anyone. A file fetched by an agent is not counted at all.