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/beko2210/context-engineering/agents-mdgit clone --depth 1 https://github.com/BEKO2210/Context-EngineeringWhat 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.00691 | $0.00691 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
Context-Engineering 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 yesterday.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Project-Wide Persistent Context
Identity
This is the Context Engineering + Closed-Loop Agent Benchmarks template repository, created by Belkis Aslani. It provides a production-grade scaffold for AI-assisted development workflows with built-in quality gates and benchmark-driven feedback loops.
Hard Rules
- Benchmark-first policy: Every change must pass
npm run benchmarkbefore merge. Score must meet or exceed the target inbenchmarks/thresholds.json. - No secrets in repo: The CI pipeline scans for leaked keys/tokens. Any match fails the build immediately.
- ESM only: All TypeScript uses ES modules. No
require(), no CommonJS. - Strict TypeScript:
strict: truein tsconfig. Noanywithout justification. - Minimal dependencies: Every new dependency must be justified. The dep scanner enforces a maximum count and a blocklist.
- Deterministic benchmarks: All benchmark runners must produce identical scores given identical input. No network calls, no randomness.
Decision Rules
- Adding a runner: Create a new file in
benchmarks/runners/, implement theBenchmarkRunnerinterface frombenchmarks/types.ts, register it inbenchmarks/run.ts. - Changing weights: Edit
benchmarks/scorecard.json. Weights must sum to 100. - Changing thresholds: Edit
benchmarks/thresholds.json. Document the reason indocs/decisions.md. - Adding orchestrator steps: Extend
tools/orchestrator/controller.tsstate machine. Document indocs/orchestrator.md.
Where to Find Things
| What | Where |
|---|---|
| Project docs | docs/ |
| Copy-paste prompts | prompts/ |
| Benchmark runners | benchmarks/runners/ |
| Benchmark config | benchmarks/scorecard.json |
| Score thresholds | benchmarks/thresholds.json |
| Orchestrator | tools/orchestrator/ |
| Reports | reports/ |
| Example project | examples/context-minimal/ |
| Lessons learned | memory/lessons.json |
| Patterns catalog | memory/patterns.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.
- yesterday First seen · 66 lines · 691 tokens per session scan A 7b9e266a0403
Context-Engineering AGENTS.md is an instructions file published in the GitHub repository BEKO2210/Context-Engineering (2 stars, last pushed 6mo ago), licensed MIT. It adds 691 tokens to every session, about $0.0035 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
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.
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).
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.