agentmods.dev

codex-mcp-server AGENTS.md

Project-specific instructions for AI coding assistants working on a TypeScript server that exposes tools and calls the Codex command-line program. They describe the source folders, build and documentation commands, and coding conventions.

In plain words
What is it for?
Use them when adding or changing server tools, utilities, shared constants, documentation, TypeScript builds, or the server's development and lint commands.
Why use it?
They clarify where new tools belong, how they must be registered, and how to build, check, test, and document the server.

Instructions file for CodexOpenCode

179 2mo ago A scan 753 tokens original MIT
View the source file cexll/codex-mcp-server
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/cexll/codex-mcp-server/agents-md
Clone the repo
git clone --depth 1 https://github.com/cexll/codex-mcp-server

Made for: Codex, OpenCode.

Per session 753 This file is loaded in full into every session.
When invoked 753 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 $0.00753 $0.00753
Opus 5 $0.00377 $0.00377
Sonnet 5 $0.00151 $0.00151
Haiku 4.5 $0.00075 $0.00075

Measured 2d ago against content hash a76a1f7f20c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

codex-mcp-server 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 63 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • src/ TypeScript sources (ESM):
    • index.ts MCP entrypoint (stdio server)
    • tools/ MCP tools (*.tool.ts), registry.ts, index.ts (registration)
    • utils/ execution, logging, parsing helpers
    • constants.ts shared types/strings
  • dist/ compiled output (generated by tsc).
  • docs/ VitePress docs.
  • scripts/ maintenance utilities (e.g., wiki deploy).

Example: add a tool under src/tools/my-feature.tool.ts, then register it in src/tools/index.ts by pushing to toolRegistry.

Build, Test, and Development Commands

  • npm run build — compile TypeScript to dist/.
  • npm start — run server from dist/.
  • npm run dev — compile once then run (no watch).
  • npm run lint — type-check only (tsc --noEmit).
  • Docs: npm run docs:dev|docs:build|docs:preview — develop/build/preview VitePress site.

Requirements: Node >=16. The server shells out to the codex CLI; ensure it's installed and authenticated in your environment.

Coding Style & Naming Conventions

  • Language: TypeScript (ESM, Node16 resolution). Imports use .js extensions in src/ to match ESM output.
  • Indentation: 2 spaces; prefer single quotes in strings except where template literals or readability favors otherwise.
  • Filenames: kebab-case. Tools end with .tool.ts (e.g., fetch-chunk.tool.ts).
  • Types: keep zod schemas colocated with tools; export a UnifiedTool and register it.

Testing Guidelines

  • Currently no automated tests (npm test is a stub). If adding tests, place them alongside sources (e.g., src/**/__tests__) and mirror filenames.
  • Aim for unit coverage on parsing/execution utilities in src/utils/ and schema validation.

Commit & Pull Request Guidelines

  • Commits: concise, imperative subject (e.g., feat: add brainstorm tool, fix(utils): handle quota errors).
  • PRs: include a clear description, linked issues, reproduction steps, and sample CLI output (stdout/stderr) when relevant.
  • Keep changes scoped; update docs in docs/ or README.md when behavior/CLI changes.

Read the full file on GitHub · 63 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. 2d ago First seen · 63 lines · 753 tokens per session scan A a76a1f7f20c8

Subscribe to this mod's changes

codex-mcp-server AGENTS.md is an instructions file published in the GitHub repository cexll/codex-mcp-server (179 stars, last pushed 2mo ago), licensed MIT. It adds 753 tokens to every session, about $0.0038 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-30.

Code reviewTestingWriting and docs
Related

Other instructions, from other repositories

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

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

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

next.js 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