What is code-executor-MCP AGENTS.md?

Repository guidelines for a TypeScript and Node.js code-execution server exposed through the Model Context Protocol, a standard way for AI tools to use external tools and data. They describe its modules, security-related files, commands, and tests.

Developing or testing sandbox executors, client pools, rate limiting, validation, MCP tool wrappers, and related server code.

They show agents where runtime code, schemas, security settings, examples, and tests belong, while giving them the commands used to build and check changes.

How aberemia24/code-executor-MCP configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to aberemia24/code-executor-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/aberemia24/code-executor-MCP/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/aberemia24/code-executor-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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/aberemia24/code-executor-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/aberemia24/code-executor-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/aberemia24/code-executor-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/aberemia24/code-executor-mcp/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/aberemia24/code-executor-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/aberemia24/code-executor-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 749 This file is loaded in full into every session.

When invoked 749 The same file — it is already loaded in full.

Security scan B 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00749	$0.00749
Opus 5.5	$0.00300	$0.00300
Sonnet 5.5	$0.00150	$0.00150
Haiku 4.5	$0.00075	$0.00075

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

Security

Grade B, and why

code-executor-MCP AGENTS.md scanned grade B with 1 finding 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.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

Configuration is managed through env vars parsed in `src/config.ts` plus optional overrides in `config/.mcp.json`; keep secrets out of version control. Update `SECURITY.md`, AppArmor/Seccomp profiles, and rate-limit defa

AGENTS.md · 25 lines

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.

Repository Guidelines

Project Structure & Module Organization

Runtime code sits in src/, where index.ts wires client pools, sandbox executors, rate limiters, and validators defined under schemas/, interfaces/, and types/; dist/ holds the compiled CLI. Reference docs, release notes, and deployment guides live in docs/, specs/, RELEASE*.md, and WORKTREE-GUIDE.md. Sample agent flows are in examples/, while operational artifacts (apparmor-profile, seccomp-profile.json, config/.mcp.json, logs/, audit.log) capture security posture. Tests live mostly in tests/ (helpers, docker checks, integrations) with a few targeted .test.ts files colocated in src/.

Build, Test, and Development Commands

npm install – install Node 22+ dependencies.
npm run dev – watch/compile TypeScript while editing.
npm run build && npm start – emit dist/ and launch the MCP server locally.
npm run generate-wrappers – regenerate tool wrappers after schema changes.
npm run typecheck and npm run lint/lint:fix – enforce strict typing and ESLint rules.
npm test, npm run test:watch, and npm run test:coverage – execute the Vitest suite and capture V8 coverage.

Coding Style & Naming Conventions

TypeScript targets ES2022 with strict + NodeNext modules; keep 2-space indentation, single quotes, kebab-case filenames, camelCase functions, and PascalCase types. Avoid any, prefer unknown plus guards or Zod schemas, and state return types on exported APIs. Keep async code await-driven, reuse helpers from src/utils.ts, and let ESLint (eslint.config.mjs) enforce import order, unused symbols, and import type patterns.

Testing Guidelines

Vitest powers both unit and integration suites. Place behavior-heavy tests in tests/ (lean on tests/helpers for fixtures and tests/integration for MCP-client exercises) and keep fast schema checks next to the source. Name specs should_<behavior>_when_<condition>. Run npm test before commits and npm run test:coverage when touching core flows; expect ≥90% coverage. Execute test-security.sh or test-docker-security.sh after sandbox or container changes.

Read the full file on GitHub · 25 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.

2mo ago First seen · 25 lines · 749 tokens per session scan B 1d191db3a5e6

Subscribe to this mod's changes

code-executor-MCP AGENTS.md is an instructions file published in the GitHub repository aberemia24/code-executor-MCP (129 stars, last pushed 11mo ago), licensed MIT. It adds 749 tokens to every session, about $0.0030 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

code-executor-MCP AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
code-executor-MCP AGENTS.mdaberemia24/code-executor-MCP	Instructions file	129	11mo ago	MIT	B	749	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

code-executor-MCP: Instructions file for Codex