Borrowing it
Nothing to install: this file belongs to kryptobaseddev/cleo. 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/kryptobaseddev/cleo/main/AGENTS.mdgit clone --depth 1 https://github.com/kryptobaseddev/cleoWrote 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/kryptobaseddev/cleo/agents-md)<a href="https://agentmods.dev/instructions/kryptobaseddev/cleo/agents-md"><img src="https://agentmods.dev/badge/instructions/kryptobaseddev/cleo/agents-md.svg" alt="Measured on agentmods" 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.06003 | $0.06003 |
| Opus 5 | $0.03002 | $0.03002 |
| Sonnet 5 | $0.01201 | $0.01201 |
| Haiku 4.5 | $0.00600 | $0.00600 |
Grade A, and why
cleo 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 2d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@~/.agents/AGENTS.md @.cleo/project-context.json
Run: cleo memory digest --brief
CLEO Project Rules (MANDATORY)
Rules below are NON-NEGOTIABLE for this repo. Protocol surface (sessions, tasks, memory, orchestration, evidence gates) is in CLEO-INJECTION.md and not duplicated here.
Code Quality
Type safety (zero tolerance). NEVER any, unknown as a shortcut, as unknown as X casting chains, or inline/mocked types. Use packages/contracts/src/ — build new contracts if genuinely missing.
DRY + SOLID. Read existing code first. Search for existing utilities before writing new ones. Centralize shared logic into lib modules. Match existing style, naming, and structure. Keep imports sorted (biome enforces).
Documentation. Add TSDoc (/** ... */) on ALL exported functions, classes, types, constants. Update existing docs — never create new ones unless necessary. Validate with forge-ts when available.
Anti-patterns (instant rejection). Claiming "tests pass" without running them. Workarounds instead of root-cause fixes. Skipping biome/lint. Creating new files when extension would do. catch (err: unknown). console.log in production. Imports without circular-dep check. Modifying test expectations to match broken code.
Quality Gates (before completing)
pnpm biome check --write . # format + lint
pnpm run build # build
pnpm run test # ZERO new failures
git diff --stat HEAD # verify scope
ANY failure → fix before completing.
Package Boundary (verify before creating/relocating files)
| Package | Purpose |
|---|---|
packages/core/ |
SDK — runtime primitives, domain logic, store, memory, sentient, gc |
packages/cleo/ |
CLI ONLY — thin dispatch + command handlers |
packages/contracts/ |
Shared types — envelope, operations, errors |
packages/cleo-os/ |
Harness — Pi/Claude-Code adapters, CleoOS runtime |
packages/caamp/ |
Agent manifest packaging (CAAMP) |
packages/studio/ |
Frontend Studio (SvelteKit) |
packages/lafs/ |
LAFS envelope spec + validator |
packages/cant/ |
.cant DSL + parser |
packages/llmtxt-core/ |
llmtxt BlobOps/AgentSession primitives |
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.
- 2d ago First seen · 304 lines · 6,003 tokens per session scan A 6dae103bb7bf
cleo AGENTS.md is an instructions file published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 16d ago), licensed MIT. It adds 6,003 tokens to every session, about $0.0300 per session on Opus 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-09-03.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.