Borrowing it
Nothing to install: this file belongs to morpho-org/sdks. 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/morpho-org/sdks/main/AGENTS.mdgit clone --depth 1 https://github.com/morpho-org/sdksWrote 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/morpho-org/sdks/agents-md)<a href="https://agentmods.dev/instructions/morpho-org/sdks/agents-md"><img src="https://agentmods.dev/badge/instructions/morpho-org/sdks/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/morpho-org/sdks/agents-md"><img src="https://agentmods.dev/badge/instructions/morpho-org/sdks/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.10834 | $0.10834 |
| Opus 5.5 | $0.04334 | $0.04334 |
| Sonnet 5.5 | $0.02167 | $0.02167 |
| Haiku 4.5 | $0.01083 | $0.01083 |
Grade A, and why
sdks 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Rules
Mission, scope, and values: see
MISSION.md. The rules below are how we build it.
Where present, CLAUDE.md is a symlink to AGENTS.md at every level — same content, two filenames so any agent finds it. Per-package AGENTS.md files refine these rules for a specific package; they may add detail but must not contradict this file. When in doubt, the root wins.
Every PR is measured against the rules below. A change that violates an architectural principle doesn't land — we question the change before we question the principle.
Enforcement note. Some rules below are enforced by tooling today (Biome formatter, knip, fork harness in
@morpho-org/test, Changesets generation). Most are review-time conventions that humans and reviewing agents apply: JSDoc on every export, layered-import bans, the §2 forbidden-patterns list (Biome'snoExplicitAnyis warn-level,noParameterAssignis disabled, and there's no rule banningas unknown as/@ts-ignore/ async-in-actions / framework imports / mocked viem clients on RPC paths), changeset-gates-CI, full coverage thresholds. Where a rule isn't backed by an automated check, treat it as binding regardless — wiring CI gates is tracked separately.
Review personas. The review-time conventions above are applied at PR review by specialized personas under
.agents/pr-review-engine/agents/, invoked by the/review-pr-{ci,gh,local}slash commands. See §10 for the full inventory and the CI/release rules they anchor. When a rule below changes, the matching persona's bullet must change with it — the backlinks on each section name the personas to update.
1. Architecture
The three pillars: layering, modularity, testability. Everything else (types, API, tests, docs) flows from getting these right.
Layering: one direction, no exceptions
Client → Entity → Action. Dependencies point one way. Lower layers never reach back into higher ones.
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 Changed · -10 lines · -3,355 tokens per session 8ef12a90de27
- 6d ago Changed · +1 lines · +258 tokens per session 9081fe438b29
- 8d ago Changed · +1 lines · +318 tokens per session 06db16df2d21
- 10d ago Changed · +4 lines · +1,360 tokens per session 2d94335e78fa
- 17d ago Changed · +1 lines · +671 tokens per session de85bb671759
- 20d ago Changed · +231 tokens per session 6d2b50916fbf
- 24d ago Changed · +213 tokens per session 1c010f2d870e
- 27d ago Changed · +1 lines · +182 tokens per session 07e9248d7eeb
- 1mo ago Changed · +1 lines · +343 tokens per session 1b401601787a
- 1mo ago First seen · 288 lines · 10,613 tokens per session scan A 8e6f1a2f0c0d
sdks AGENTS.md is an instructions file published in the GitHub repository morpho-org/sdks (44 stars, last pushed yesterday), licensed MIT. It adds 10,834 tokens to every session, about $0.0433 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-09-01.
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.