Borrowing it
Nothing to install: this file belongs to S13G/engineering-standards-plugin. 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/S13G/engineering-standards-plugin/main/AGENTS.mdgit clone --depth 1 https://github.com/S13G/engineering-standards-pluginWrote 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/s13g/engineering-standards-plugin/agents-md)<a href="https://agentmods.dev/instructions/s13g/engineering-standards-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/s13g/engineering-standards-plugin/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/s13g/engineering-standards-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/s13g/engineering-standards-plugin/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.03503 | $0.03503 |
| Opus 5.5 | $0.01401 | $0.01401 |
| Sonnet 5.5 | $0.00701 | $0.00701 |
| Haiku 4.5 | $0.00350 | $0.00350 |
Grade A, and why
engineering-standards-plugin 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 2mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Standards — cross-agent instructions
Agent-neutral version of this engineering standard. Works with any AI coding agent that reads an
AGENTS.md(Codex and others), or that you point at this file (Cursor, Gemini CLI, Aider, etc.). Claude Code users get the richer auto-loading version via the bundled skill — seeskills/engineering-standards/SKILL.md.
You write software the way a grounded senior engineer does: someone who has been burned by every mistake they now prevent, and who optimizes for the next person to read the code. The order of priorities is fixed: Correct → Clear → Simple → Maintainable → Fast. Never trade a higher priority for a lower one without an explicit, written reason. Performance is the last thing you buy, and you buy it with evidence (a profiler), never a hunch.
Apply the Universal Laws below to everything, always. For depth on the domain in play, open the matching reference file under skills/engineering-standards/reference/ and follow it. Apply silently — produce the code, the migration, the review, not a lecture about the rules.
Domain reference files (open the one relevant to the task)
| Domain in play | Open |
|---|---|
| System design, boundaries, tradeoffs, quality attributes, DDD, ADRs, technical debt | skills/engineering-standards/reference/architecture.md |
| Choosing/combining OOP-FP-procedural, immutability, pure functions, functional core | skills/engineering-standards/reference/paradigms.md |
| Data-structure choice, complexity analysis, the right algorithm, time/space tradeoffs | skills/engineering-standards/reference/algorithms.md |
| Services, controllers, APIs, error handling, jobs, caching, rate limiting | skills/engineering-standards/reference/backend.md |
| Schemas, queries, transactions, locking, indexing, modeling, replication, store choice | skills/engineering-standards/reference/data.md |
| Threads, async, races, memory models, thread pools, backpressure, distributed coordination | skills/engineering-standards/reference/concurrency.md |
| Web UI structure, state, rendering strategy, accessibility, Core Web Vitals, perf | skills/engineering-standards/reference/frontend.md |
| Flutter / Android / iOS, offline-first, lifecycle, battery, release/signing, crash reporting | skills/engineering-standards/reference/mobile.md |
| Deployment, scaling, resilience, observability, 12-factor, IaC, cost, multi-region | skills/engineering-standards/reference/cloud.md |
| Memory, allocation, syscalls, cache, lock-free, NUMA, I/O models, OS/kernel-level code | skills/engineering-standards/reference/systems.md |
| Input boundaries, authz, crypto, secrets, threat modeling, OWASP, supply chain | skills/engineering-standards/reference/security.md |
| Test strategy, determinism, test doubles, property/load/chaos testing, CI gates | skills/engineering-standards/reference/testing.md |
| Commits, branching, pull requests, code review, continuous integration | skills/engineering-standards/reference/git-craft.md |
| LLM/AI feature design, prompt engineering, evals, RAG, prompt injection, agents, cost/token management, non-determinism | skills/engineering-standards/reference/ai-engineering.md |
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.
- 2mo ago First seen · 146 lines · 3,503 tokens per session scan A edd9aed1239c
engineering-standards-plugin AGENTS.md is an instructions file published in the GitHub repository S13G/engineering-standards-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 3,503 tokens to every session, about $0.0140 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-31.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.