mcp-drift-lab: Instructions file for Codex

AGENTS.md

mcp-drift-lab AGENTS.md is an instructions file for Codex, OpenCode from zelinsky-alexander/mcp-drift-lab. It costs 272 tokens per session, scanned A, original, MIT.

Project instructions that require a coding agent to inspect a task and present a plan before changing a project. The agent must wait for explicit approval before editing files, running changing commands, or installing packages.

In plain words
What is it for?
Planning code changes, identifying affected files and risks, getting approval, implementing only the approved work, and reporting tests or remaining issues.
Why use it?
They give the developer a review point before work begins and help keep implementation within the agreed scope. They also require a summary and validation after approved changes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Codex.

This is zelinsky-alexander/mcp-drift-lab's own configuration. It tells Codex and OpenCode how to work on mcp-drift-lab itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-drift-lab configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zelinsky-alexander/mcp-drift-lab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zelinsky-alexander/mcp-drift-lab/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/zelinsky-alexander/mcp-drift-lab

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for mcp-drift-lab AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/zelinsky-alexander/mcp-drift-lab/agents-md/github.svg)](https://agentmods.dev/instructions/zelinsky-alexander/mcp-drift-lab/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/zelinsky-alexander/mcp-drift-lab/agents-md"><img src="https://agentmods.dev/badge/instructions/zelinsky-alexander/mcp-drift-lab/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.

agentmods 80×15 button for mcp-drift-lab AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/zelinsky-alexander/mcp-drift-lab/agents-md"><img src="https://agentmods.dev/badge/instructions/zelinsky-alexander/mcp-drift-lab/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 272 This file is loaded in full into every session.
When invoked 272 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00272 $0.00272
Opus 5.5 $0.00109 $0.00109
Sonnet 5.5 $0.00054 $0.00054
Haiku 4.5 $0.00027 $0.00027

Measured 2mo ago against content hash 3bbd40b8b9bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-drift-lab 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.

AGENTS.md · 43 lines

What it actually says

Codex Working Rules

Plan before action

For every task:

  1. First inspect the relevant files and understand the existing implementation.

  2. Do not modify files, generate code, run commands, install packages, create files, delete files, or change configuration yet.

  3. Present a concise implementation plan that includes:

    • your understanding of the task;
    • files likely to be affected;
    • proposed changes;
    • important design decisions;
    • possible risks or uncertainties;
    • tests or validation that should be performed.
  4. Stop after presenting the plan.

  5. Wait for my explicit approval before making any changes or running any command that can alter the project.

Only proceed when I clearly say something such as:

  • “Approved”
  • “Proceed”
  • “Implement the plan”

If I request changes to the plan, revise the plan and wait for approval again.

Execution after approval

After approval:

  1. Implement only the approved scope.

  2. Do not add unrelated improvements or refactoring.

  3. Ask before making a significant deviation from the approved plan.

  4. After implementation, summarize:

    • files changed;
    • changes made;
    • commands or tests run;
    • remaining issues or recommended follow-up work.

Explicit approval is required for each new task. Approval of one plan does not authorize future tasks.

Changes

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.

  1. 2mo ago First seen · 43 lines · 272 tokens per session scan A 3bbd40b8b9bf

Subscribe to this mod's changes

mcp-drift-lab AGENTS.md is an instructions file published in the GitHub repository zelinsky-alexander/mcp-drift-lab (0 stars, last pushed 3mo ago), licensed MIT. It adds 272 tokens to every session, about $0.0011 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.

Related

mcp-drift-lab AGENTS.md compared with instructions from other repositories

mcp-drift-lab AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
mcp-drift-lab AGENTS.mdzelinsky-alexander/mcp-drift-labInstructions file03mo agoMITA272Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,685GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot