Borrowing it
Nothing to install: this file belongs to kstenerud/yoloai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kstenerud/yoloai/main/AGENTS.mdgit clone --depth 1 https://github.com/kstenerud/yoloaiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/kstenerud/yoloai/agents-md)<a href="https://agentmods.dev/instructions/kstenerud/yoloai/agents-md"><img src="https://agentmods.dev/badge/instructions/kstenerud/yoloai/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/kstenerud/yoloai/agents-md"><img src="https://agentmods.dev/badge/instructions/kstenerud/yoloai/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.03522 | $0.03522 |
| Opus 5.5 | $0.01409 | $0.01409 |
| Sonnet 5.5 | $0.00704 | $0.00704 |
| Haiku 4.5 | $0.00352 | $0.00352 |
Grade A, and why
yoloai AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 14d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
yoloAI runs AI coding CLI agents inside disposable sandboxes (containers, Tart VMs, macOS Seatbelt) with a copy/diff/apply workflow. Go binary, no runtime deps beyond the backend. Public beta: breaking changes are allowed, but must be recorded — rule 1.
This is the contract for changing yoloAI, and the canonical instruction file for every agent
working on it. CLAUDE.md imports it. Keep it short; detail lives behind the pointers.
Docs last swept: 2026-07-15 (D116, D124). Docs drift silently — nothing executes prose. If
that date is more than ~3 months ago, say so, unprompted, before relying on a doc being right.
Bump it when a sweep lands. Why this exists: general-principles.md §16.
Deprecations reviewed: 2026-07-17 (D127) — nothing due; next 2026-09-12. Compatibility code
is invisible once written, so it is never retired. docs/contributors/deprecations.md registers
each with the date it was incurred and a per-entry due date. If today is past the date above,
read the register and say so, unprompted — the owner decides what retires, but only if asked.
This is a nag, not a gate: nothing fails, ever. Bump the date when a review lands.
The marker is a claim, so treat it as one. When first written it named a sweep that had never
opened architecture/, which at that moment documented a mode retired two releases earlier and
a package that has never existed — the drift-detector's own first reading was wrong. D124 made
it true and gated the names, so architecture/ now fails loudly rather than drifting quietly.
No other tier has that backstop.
Where things are
Docs are organised by role. Pick your tier, then read that directory's README.md:
| Tier | Directory |
|---|---|
| Users — running yoloAI | docs/ |
| Integrators — embedding it as a library | docs/integrators/ |
| Contributors — changing it | docs/contributors/ |
Two you will want by name: architecture/where-to-change.md maps a change onto the files
that make it. backend-idiosyncrasies.md catalogues backend behaviour that contradicts its
own docs — read it before diagnosing any backend problem; add to it when you find more.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 14d ago Changed · -11 lines · -249 tokens per session 8b2a33713c69
- 1mo ago First seen · 190 lines · 3,771 tokens per session scan A ba253e03ff41
yoloai AGENTS.md is an instructions file published in the GitHub repository kstenerud/yoloai (221 stars, last pushed 15d ago), licensed MIT. It adds 3,522 tokens to every session, about $0.0141 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.