airlock-mcp: Instructions file for Codex

AGENTS.md

airlock-mcp AGENTS.md is an instructions file for Codex, OpenCode from reunionstudio/airlock-mcp. It costs 511 tokens per session, scanned A, original, Apache-2.0.

A set of project instructions for working with Airlock MCP, an interface that lets coding agents build specifications and work with governed data.

In plain words
What is it for?
Use it when developing Airlock MCP, registering agents, defining how data may be read or changed, and verifying specification-building workflows.
Why use it?
It keeps the project focused on its intended boundaries, installation process, agent behavior, and checks for specification drafts.

Instructions file for CodexOpenCode

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

This is reunionstudio/airlock-mcp's own configuration. It tells Codex and OpenCode how to work on airlock-mcp 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 airlock-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to reunionstudio/airlock-mcp. 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/reunionstudio/airlock-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/reunionstudio/airlock-mcp

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 airlock-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/reunionstudio/airlock-mcp/agents-md.svg)](https://agentmods.dev/instructions/reunionstudio/airlock-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/reunionstudio/airlock-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/reunionstudio/airlock-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 511 This file is loaded in full into every session.
When invoked 511 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.00511 $0.00511
Opus 5 $0.00255 $0.00255
Sonnet 5 $0.00102 $0.00102
Haiku 4.5 $0.00051 $0.00051

Measured 6d ago against content hash be0c77de6ffe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

airlock-mcp 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 6d 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 · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Airlock MCP Guidance

Airlock MCP is the single installed interface for AI agents working with Airlock. It should cover building specs, using specs, pulling and pushing governed data, and discovering improvements from real use cases.

Spec building is bundled inside Airlock MCP, not a second thing users install.

Product Boundary

  • Keep this repo focused on connector installation, MCP server behavior, agent registration, Airlock-facing tools, spec drafting patterns, workspace files, and deterministic spec-building checks.
  • The public user command is npx @reunionstudio/airlock-mcp install.
  • For Codex, install should use codex mcp add airlock -- npx -y @reunionstudio/airlock-mcp server.
  • After install, the user creates a blank <project>-specs Codex project and starts chatting there. They should ask for Airlock, not for a separate spec-building install.
  • Current installed Airlock separates procedure intent: observe.* is the read-only governance observation surface, agent.* is governed actor work, and admin.* is administrative mutation. App and audit guidance should prefer observe payloads for discovery, health, access explanation, activity, billing events, governance maps, and context packets.

MCP Runtime

  • The current Node server is a small bootstrap server for the one-install Airlock MCP experience.
  • It documents, but does not proxy, the optional Snowflake-managed MCP endpoints exposed by installed Airlock. Keep their fixed read-only tool and identity boundary discoverable at airlock://native-app-managed-mcp.
  • Prefer Rust with rmcp for the production MCP server once tools do real operational work beyond setup guidance, such as validating specs, loading records, reading outputs, handling attachments, or coordinating push/pull workflows.
  • For stdio MCP, stdout is protocol-only. Send logs and diagnostics to stderr.
  • Test the stdio server with raw JSON-RPC messages for initialize, tools/list, prompts/list, resources/list, and resources/read.

Read the full file on GitHub · 51 lines

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. 6d ago First seen · 51 lines · 511 tokens per session scan A be0c77de6ffe

Subscribe to this mod's changes

airlock-mcp AGENTS.md is an instructions file published in the GitHub repository reunionstudio/airlock-mcp (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 511 tokens to every session, about $0.0026 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

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

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

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

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

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