Borrowing it
Nothing to install: this file belongs to linkpranay-ai/context-engineering-protocol. 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/linkpranay-ai/context-engineering-protocol/main/AGENTS.mdgit clone --depth 1 https://github.com/linkpranay-ai/context-engineering-protocolWrote 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/linkpranay-ai/context-engineering-protocol/agents-md)<a href="https://agentmods.dev/instructions/linkpranay-ai/context-engineering-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/linkpranay-ai/context-engineering-protocol/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/linkpranay-ai/context-engineering-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/linkpranay-ai/context-engineering-protocol/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.01388 | $0.01388 |
| Opus 5.5 | $0.00555 | $0.00555 |
| Sonnet 5.5 | $0.00278 | $0.00278 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
context-engineering-protocol 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 1mo 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 — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents (e.g. OpenAI Codex) working in this repository.
This repository packages its capabilities as portable "skills" - read the
relevant skill's SKILL.md in full and follow it before acting in the
corresponding area. Do not guess at a skill's behavior from this table alone.
| Skill | Description | Path |
|---|---|---|
| compiling-project-guidelines | Compile scattered guideline sources into one scope-aware COMPILED-GUIDELINES.md for other skills and ult-context-generate's Constraints layer. Do NOT use to enforce rules at runtime. | .github/skills/compiling-project-guidelines/SKILL.md |
| demo-consume-context | Worked example that discovers, loads, and tags a context package per CONSUMING-CONTEXT-PACKAGE.md, then writes a reverse-index addendum — proves the produce/consume/tag loop end-to-end. Do NOT use for real feature work. | .github/skills/demo-consume-context/SKILL.md |
| demo-write-user-stories | Reference implementation that writes functional user stories from a feature description, optionally grounded in an approved CEP context package per CONSUMING-CONTEXT-PACKAGE.md, with per-story citations and the standard tag/reverse-index loop. A worked example for downstream teams building their own context-consuming skills. | .github/skills/demo-write-user-stories/SKILL.md |
| ult-autoscaffold-content | Generate real starter content for a project's What-L2 (requirements) and How-L2 (architecture/conventions) CEP layers once ult-repo-layout has resolved their paths but found them empty — an honest, minimal, YAML-frontmatter-first overview document per layer for small/single targets, or graphify-informed per-module tiering with resumable per-module CONTEXT.md generation, existence-gated CODING-STANDARDS.md/TESTING-GUIDELINES.md, interface-boundary docs for graph-crossing module pairs, and a rendered CEP-INDEX.md router for large repos, optionally informed by a user-supplied domain-pack of terminology/references if one is configured. This skill generates a NEW starter doc only when none exists — it never compiles or reconciles EXISTING scattered guideline sources (that's compiling-project-guidelines' job). Do NOT use to enforce layout paths or run layer discovery — that's ult-repo-layout. Do NOT use to author or generate a domain pack — this skill only ever consumes one you already wrote. | .github/skills/ult-autoscaffold-content/SKILL.md |
| ult-cep-retrofit | Point at an existing skill library, inventory it format-agnostically, and (with human confirmation at every step) insert pointers to CEP's existing CONSUMING-.md contracts into the skills that should consume them. Do NOT use to write new CONSUMING-.md contracts, validate that a retrofit works at runtime, or edit a library's own logic beyond the inserted pointer. | .github/skills/ult-cep-retrofit/SKILL.md |
| ult-cep-wizard | Launch a local, localhost-only browser wizard with two journeys — layout onboarding for a project with ult-repo-layout installed, initialized or not — guides an uninitialized or not-yet-discovered repo through Run Discover, then shows resolved layer/slot state through four labeled boxes and a directory picker, and lets you resolve pending layout decisions (confirm/skip/disable/pick-a-directory) and Apply them into context-config.yaml via ult-repo-layout's own confirm step; and retrofit — walks an existing skill library through ult-cep-retrofit's inventory/classify/draft/apply flow, with an editable per-file diff preview and batch Apply, never writing without that preview. Do NOT use for headless/CI-only layout validation — use ult-repo-layout's discover/confirm-layers/--validate directly. | .github/skills/ult-cep-wizard/SKILL.md |
| ult-codegraph | Generate a codebase knowledge graph with graphify at graphify-out/ so other skills can query cross-file relationships before touching code. Do NOT use for runtime profiling. |
.github/skills/ult-codegraph/SKILL.md |
| ult-context-generate | Assemble a context package (code graph, requirements, constraints, blast radius) before a downstream generation task runs - human-approved, source-attributed. Do NOT use for simple lookups. | .github/skills/ult-context-generate/SKILL.md |
| ult-institutional-memory-distill | Distill decisions, reasoning, and rejected alternatives from PRs, design docs, and postmortems into the project's decision_ledger, so ult-context-generate's trip-wire can surface institutional memory before new work quietly repeats settled ground. Do NOT use to query the ledger against new work or decide revise/proceed/escalate -- that's ult-context-generate/SKILL.md Step 7.7's job. | .github/skills/ult-institutional-memory-distill/SKILL.md |
| ult-onboarding-index | Discover CEP-managed content already present in a target repo (What/How layer docs, compiled guidelines, context packages, decision ledger) via existence checks against layout-slots-registry.yaml-resolved paths, then write one canonical root AGENTS.md onboarding index plus thin per-tool pointer stubs (.github/copilot-instructions.md, CLAUDE.md, .cursor/rules/onboarding.mdc) that link into it. All writes are marked-block or existence-gated and non-destructive, including install.sh's own AGENTS.md skill-catalog block. Codex needs no separate stub -- root AGENTS.md is already its native onboarding format. Do NOT use it to generate the CEP content itself (ult-autoscaffold-content/compiling-project-guidelines do that) or to resolve layer paths (ult-repo-layout does that). Do NOT confuse it with this OSS repo's own AGENTS.md (generated by catalog/export_adapters.py) -- this skill only ever writes into a separate target repo being onboarded with CEP. | .github/skills/ult-onboarding-index/SKILL.md |
| ult-repo-layout | Register, resolve, and validate where a project's path-slots actually live via .layout-slots.yaml markers, so relocating a slot needs zero SKILL.md edits. Do NOT use for single-file lookups. | .github/skills/ult-repo-layout/SKILL.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.
- 1mo ago First seen · 25 lines · 1,388 tokens per session scan A 9421fe87cdf1
context-engineering-protocol AGENTS.md is an instructions file published in the GitHub repository linkpranay-ai/context-engineering-protocol (10 stars, last pushed 26d ago), licensed Apache-2.0. It adds 1,388 tokens to every session, about $0.0056 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
agent-rulescope copilot-instructions.md
Copilot instructions for 13624725933/agent-rulescope, a project described as: See exactly which instructions your coding agent inherits. Scan AGENTS.md, CLAUDE.md, Cursor and Copilot rules.
agent-rulescope tests.instructions.md
Instructions for 13624725933/agent-rulescope, a project described as: See exactly which instructions your coding agent inherits. Scan AGENTS.md, CLAUDE.md, Cursor and Copilot rules.
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.