Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/0ryant/engineering-doctrine/agents-mdgit clone --depth 1 https://github.com/0ryant/engineering-doctrineWhat 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 | $0.00438 | $0.00438 |
| Opus 5 | $0.00219 | $0.00219 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
engineering-doctrine 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.
What it actually says
Agent instructions (engineering-doctrine)
This repository is the canonical engineering-doctrine library (Markdown principles, patterns, tooling, checklists). When a task adds or substantially changes doctrine/, docs/adr/, or the umbrella ENGINEERING.md, follow the library change harness:
- Semantic index / ingestion map: doctrine/SEMANTIC_INDEX.md. Before substantive analysis or edits, read its Critical Agent Context and the matching Task Route so the right principle / pattern / tooling / checklist / ADR files are in context.
- Full procedure: doctrine/patterns/doctrine-library-change-harness.md
- Checklist: doctrine/checklists/doctrine-change-checklist.md
- Preflight:
./scripts/doctrine-change-preflight.shfrom the repo root
Minimum bar for meaningful additions: researched basis (citations and/or doctrine/evolution/ note), an ADR (new or explicitly referenced), correct layering with cross-links between principle / pattern / tooling, and navigation updates (sitemap via script, glossary.md, REFERENCES.md, doctrine/README.md as appropriate). Use the copy-paste prompt in harness §7 for structured agent tasks.
Portability boundary: do not name organisation-private products, portfolio
tools, internal repositories, or local programme artefacts anywhere in the
publishable library. Express the capability or control generically. External
standards and vendor material may be named only as cited grounding or clearly
optional illustration. Keep local work records under ignored .local/ paths.
Not applicable: drive-by rewrites, vendor pitches in principles/, or new normative “musts” without consumer-impact labelling. See CONTRIBUTING.md and GOVERNANCE.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.
- 2d ago First seen · 19 lines · 438 tokens per session scan A 611f889350c1
engineering-doctrine AGENTS.md is an instructions file published in the GitHub repository 0ryant/engineering-doctrine (5 stars, last pushed 21d ago), licensed Apache-2.0. It adds 438 tokens to every session, about $0.0022 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-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).
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.