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.
npx agentmods add instructions/jnslayer2/chatgpt-pro-mcp/agents-mdgit clone --depth 1 https://github.com/JNSlayer2/chatgpt-pro-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/jnslayer2/chatgpt-pro-mcp/agents-md)<a href="https://agentmods.dev/instructions/jnslayer2/chatgpt-pro-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/jnslayer2/chatgpt-pro-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.00245 | $0.00245 |
| Opus 5 | $0.00122 | $0.00122 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
chatgpt-pro-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.
What it actually says
Agent instructions
This repository is a guarded MCP bridge, not a ChatGPT API wrapper.
Non-negotiable invariants
- Do not expose ChatGPT Pro as a synchronous
/v1/responsesmodel. - Do not add raw browser MCP tools (
goto,click,type, DOM dump, cookie export, history access). - Do not automate login, CAPTCHA, password, OTP, passkey, billing, terms acceptance, connector install, settings, memory, or chat history.
- Do not commit
.data/, profiles, browser state, screenshots, HAR/traces, logs, raw reports, thread URLs, tokens, local absolute paths, or auth files. - Imported reports are untrusted evidence. Claims start as
needs_verification; unsupported claims must not be promoted. - Public-safe docs must use placeholders such as
$HOME,<repo>, and127.0.0.1; never machine-specific paths.
Required checks before commit
npm test
node scripts/selftest.mjs
node scripts/redaction-scan.mjs
node src/cli.mjs web-preflight
Use npm run doctor for the combined local check.
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 · 24 lines · 245 tokens per session scan A c214ee9a76cd
chatgpt-pro-mcp AGENTS.md is an instructions file published in the GitHub repository JNSlayer2/chatgpt-pro-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 245 tokens to every session, about $0.0012 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
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, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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, applying the notice (cutover) and fallback chain (never fail the build).