Borrowing it
Nothing to install: this file belongs to MisakiSenpa1/adaptive-coding-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.
curl -O https://raw.githubusercontent.com/MisakiSenpa1/adaptive-coding-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/MisakiSenpa1/adaptive-coding-mcpWrote 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.
[](https://agentmods.dev/instructions/misakisenpa1/adaptive-coding-mcp/agents-md)<a href="https://agentmods.dev/instructions/misakisenpa1/adaptive-coding-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/misakisenpa1/adaptive-coding-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.00739 | $0.00739 |
| Opus 5 | $0.00369 | $0.00369 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
adaptive-coding-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 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adaptive Coding MCP Agent Instructions
Read this file first, then read research/PROJECT_STATE.md and
research/DEVLOG.md before making changes.
Mission
Build a reliable, persistent, auditable MCP harness that lets the ChatGPT web client remain the primary coding agent. The bootstrap phase may use Codex as an engineering executor, but Codex is not part of the measured ChatGPT-only system.
Repository roles
main: reviewed stable bootstrap state.bootstrap/codex: candidate implementation work performed by desktop Codex.research/chatgpt: ChatGPT + MCP research and experiment preparation.rescue/maintenance: recovery-only fixes when the harness is unavailable.experiment/*: later frozen benchmark versions; do not create them casually.
Work only on the branch assigned to the current worktree. Never force-push or
rewrite shared history. Do not merge into main; leave a reviewable commit for
ChatGPT and the operator.
Mandatory safety boundaries
- Do not modify, stop, restart, redeploy, or reconfigure the production Coding Tools MCP service.
- Do not edit outside the current worktree unless the task explicitly names a repository-owned test/result directory.
- Do not use root or modify firewall, systemd, SSH, or operating-system config.
- Do not read, print, copy, or commit secrets,
.envfiles, tokens, SSH keys, browser credentials, or production configuration. - Do not add a second primary model, autonomous agent loop, or Hermes runtime.
- Keep worker-model support disabled by default and optional in every design.
- Do not deploy a server as part of a coding task.
Engineering rules
- Preserve upstream Coding Tools MCP semantics in the V0 profile.
- Prefer deterministic, bounded, inspectable behavior over model-generated inference inside the harness.
- New tools must have synchronized registry metadata, input schemas, runtime handlers, documentation, annotations, and schema-drift tests.
- Persistent state must use explicit schemas, transactions, bounded storage, safe paths, and auditable records.
- Full command output and checkpoints require quotas and retention controls.
- Avoid unnecessary dependencies. Do not install Hermes dependencies, compile Codex, or introduce Docker merely for development convenience.
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.
- 5d ago First seen · 87 lines · 739 tokens per session scan A fdf213275a59
adaptive-coding-mcp AGENTS.md is an instructions file published in the GitHub repository MisakiSenpa1/adaptive-coding-mcp (0 stars, last pushed 10d ago), licensed Apache-2.0. It adds 739 tokens to every session, about $0.0037 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.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.