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

Install

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.

agentmods
npx agentmods add instructions/zelinsky-alexander/mcp-drift-lab/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.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.svg" alt="Measured on agentmods" 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. Scan, not verified.
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 $0.00136 $0.00136
Sonnet 5 $0.00054 $0.00054
Haiku 4.5 $0.00027 $0.00027

Measured 5d ago against content hash 3bbd40b8b9bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 5d 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. 5d 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 1mo ago), licensed MIT. It adds 272 tokens to every session, about $0.0014 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.

Related

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

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,182 tokens

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

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens