Borrowing it
Nothing to install: this file belongs to menaje/codex-mcp-bridge-for-chatgpt. 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/menaje/codex-mcp-bridge-for-chatgpt/dev/AGENTS.mdgit clone --depth 1 https://github.com/menaje/codex-mcp-bridge-for-chatgptWrote 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/menaje/codex-mcp-bridge-for-chatgpt/agents-md)<a href="https://agentmods.dev/instructions/menaje/codex-mcp-bridge-for-chatgpt/agents-md"><img src="https://agentmods.dev/badge/instructions/menaje/codex-mcp-bridge-for-chatgpt/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.
<a href="https://agentmods.dev/instructions/menaje/codex-mcp-bridge-for-chatgpt/agents-md"><img src="https://agentmods.dev/badge/instructions/menaje/codex-mcp-bridge-for-chatgpt/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00407 | $0.00407 |
| Opus 5.5 | $0.00163 | $0.00163 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
codex-mcp-bridge-for-chatgpt 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 yesterday.
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.
What it actually says
Repository work lifecycle
- Create task branches and worktrees when they help isolate work. Choose the integration target when starting:
devfor ordinary development, or the explicitly requested parent branch. Follow release governance for release branches andmain. - For a target other than
dev, runnode .codex/hooks/git-lifecycle.mjs set-target <branch>from each task worktree. The hook stores that choice in worktree Git metadata. Set it in the checkout used for later branch cleanup as well. - Before reporting a code-changing task as complete, verify that its changes are committed and integrated into the chosen target branch. A finished Codex turn or handoff does not establish Git integration.
- After integration, remove only the task branch and task-owned worktrees that can be safely removed independently of the Codex conversation. Check for uncommitted files, unmerged commits, open work, and other users or processes of the worktree before removal. Never use force deletion to bypass a failed check.
- If integration or cleanup remains pending, preserve the work and state exactly what remains in the final response. Squash and cherry-pick integration require explicit evidence because commit ancestry alone will not prove them.
- Codex conversations are outside this Git lifecycle. Do not archive, unarchive, pin, unpin, hide, rename, move, or delete any conversation, including the current one, unless the user explicitly requests that conversation action. Never use conversation archiving to clean a worktree. Codex-managed worktrees follow the app's existing cleanup setting; if immediate removal would affect a conversation, leave the worktree and report cleanup as pending. Remove permanent or manually created worktrees separately after the same checks.
The project Codex hooks in .codex/hooks.json provide a read-only end-of-turn check and a guard for common Git deletion commands. They do not merge branches or remove worktrees automatically, and they are not a complete Git enforcement boundary.
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.
- yesterday First seen · 11 lines · 407 tokens per session scan A fc832af4d0f2
codex-mcp-bridge-for-chatgpt AGENTS.md is an instructions file published in the GitHub repository menaje/codex-mcp-bridge-for-chatgpt (1 stars, last pushed yesterday), licensed MIT. It adds 407 tokens to every session, about $0.0016 per session on Opus 5.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-09-24.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, repository design references, quickstart — add a new integration in 5 steps and integration architecture.
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).