Borrowing it
Nothing to install: this file belongs to evgenyvinnik/llm-driven-system-design. 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/evgenyvinnik/llm-driven-system-design/main/AGENTS.mdgit clone --depth 1 https://github.com/evgenyvinnik/llm-driven-system-designWrote 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/evgenyvinnik/llm-driven-system-design/agents-md)<a href="https://agentmods.dev/instructions/evgenyvinnik/llm-driven-system-design/agents-md"><img src="https://agentmods.dev/badge/instructions/evgenyvinnik/llm-driven-system-design/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.07701 | $0.07701 |
| Opus 5 | $0.03851 | $0.03851 |
| Sonnet 5 | $0.01540 | $0.01540 |
| Haiku 4.5 | $0.00770 | $0.00770 |
Grade A, and why
llm-driven-system-design 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- llm-driven-system-design CLAUDE.md — 98% identical, 16 lines differ
How it starts
The opening of the file, as written. The whole thing — 699 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.
Table of Contents
- Repository Overview
- Quick Start for Any Project
- Project Structure
- Common Commands
- Repository Scripts
- CI/CD
- Technology Stack Defaults
- Key Design Principles
- Port Conventions
- Frontend Best Practices
- Backend Architecture Pattern
- Database Selection Guide
- Creating New Projects
- Local Development Philosophy
- Infrastructure Options
- ESM Import Convention
Repository Overview
This is a system design learning repository where each subdirectory represents an independent system design challenge. Most projects have both design documentation and working implementations.
Node.js Requirement: >=20.0.0
Quick Start for Any Project
- Read the project's
architecture.mdfirst to understand the design - Check
AGENTS.mdfor iteration history and key decisions (primary source of truth for project-specific guidance - captures the "why" behind implementation choices) - Look at
README.mdfor setup instructions - Check
package.jsonto find available scripts
Project Structure
Each project folder typically contains:
<project>/
├── README.md # Setup instructions and implementation guide
├── architecture.md # System design documentation and trade-offs
├── system-design-answer-frontend.md # Frontend-focused interview answer
├── system-design-answer-backend.md # Backend-focused interview answer
├── system-design-answer-fullstack.md # Full-stack interview answer
├── AGENTS.md # LLM collaboration notes and iteration history
├── frontend/ # React + TypeScript frontend (when applicable)
├── backend/ # Node.js + Express backend (when applicable)
├── training/ # ML training code (Python, when applicable)
└── docker-compose.yml # Infrastructure services (PostgreSQL, Redis, etc.)
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.
- 7d ago First seen · 699 lines · 7,701 tokens per session scan A f5dd6040ea42
llm-driven-system-design AGENTS.md is an instructions file published in the GitHub repository evgenyvinnik/llm-driven-system-design (55 stars, last pushed 26d ago), licensed MIT. It adds 7,701 tokens to every session, about $0.0385 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-08-30.
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.