Borrowing it
Nothing to install: this file belongs to saadnvd1/agent-os. 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/saadnvd1/agent-os/main/AGENTS.mdgit clone --depth 1 https://github.com/saadnvd1/agent-osWrote 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/saadnvd1/agent-os/agents-md)<a href="https://agentmods.dev/instructions/saadnvd1/agent-os/agents-md"><img src="https://agentmods.dev/badge/instructions/saadnvd1/agent-os/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/saadnvd1/agent-os/agents-md"><img src="https://agentmods.dev/badge/instructions/saadnvd1/agent-os/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.00805 | $0.00805 |
| Opus 5.5 | $0.00322 | $0.00322 |
| Sonnet 5.5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
agent-os 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 9d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code rules
Every agent working in this repo follows these. Each rule has its reason.
Code style
- TypeScript everywhere, never
any. Why: types are the cheapest test we have. - Absolute imports:
@/lib/x, not../lib/x. Why: a file can move without its imports breaking. - No unnecessary comments; comment only the why. No strong borders: use shadows and spacing.
- React Query for server state,
useStatefor local state, Valtio for shared UI state, Context sparingly. UseisPending(notisLoading) and always show skeletons on the initial load. - Purple theme (HSL hue 270).
- Mobile first: the primary device is a phone. Touch targets are at least 44x44px, single pane with bottom tabs, unified diffs.
Structure
- Shared design-system components. A UI element used in more than one place becomes a generic wrapper in
components/ui/around the shadcn/Radix primitive (button, callout/notice, status badge, etc.), and call sites use the wrapper. Notices and status pills always use the shared component, never hand-built markup. Why: one place to change how it looks and behaves. - API routes. Validate request input with a zod schema. Routes stay thin orchestrators: business logic lives in
lib/, and database access goes through the queries layer, not inline SQL in the route. This applies to new routes and any route you touch; don't bulk-migrate the existing ones. Why: input is checked once, at the edge, and logic can be tested without HTTP. - Business logic as functional modules in
lib/<domain>/<feature>/:index.ts(public exports),types.ts, one file per action named as a verb (startTask.ts,placeTask.ts), andutils.tsif needed. Export plain functions, not classes with static methods; no React inlib/. Why: a feature is easy to find, import and test. - Components. Break large components into sub-components, with a folder per component once it has parts. Extract a hook only when it's used in more than one place. Why: small pieces stay readable, and a hook with one caller is indirection.
- File length. A source file stays under ~900 lines. Past that, split it by responsibility. A file may exceed it only with a stated reason (a generated file, a single table of data). Why: files this size are where changes start colliding and review stops being possible.
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.
- 9d ago Changed · +1 lines · +134 tokens per session 1120a19e5051
- 13d ago First seen · 28 lines · 671 tokens per session scan A 1877da6616a7
agent-os AGENTS.md is an instructions file published in the GitHub repository saadnvd1/agent-os (11 stars, last pushed today), licensed MIT. It adds 805 tokens to every session, about $0.0032 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-10-16.
Other instructions, from other repositories
create-trimble-app typescript.instructions.md
Instructions for julianoczkowski/create-trimble-app, covering typescript patterns for modus components, event type casting, common event types, component ref types and modal ref pattern.
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).