opgg-mcp: Instructions file for Codex

AGENTS.md

opgg-mcp AGENTS.md is an instructions file for Codex, OpenCode from opgginc/opgg-mcp. It costs 974 tokens per session, scanned A, original, MIT.

Repository instructions for opgg-mcp, a small proxy that connects local standard input/output to a remote OP.GG MCP server. MCP is a standard way for AI agents to access tools.

In plain words
What is it for?
Use them when changing the proxy, its capability bridge, build setup, deployment files, or synchronized language documentation.
Why use it?
They explain where the proxy code and documentation live and give the required commands and workflow rules for building and testing it.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is opgginc/opgg-mcp's own configuration. It tells Codex and OpenCode how to work on opgg-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything opgg-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to opgginc/opgg-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/opgginc/opgg-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/opgginc/opgg-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.

agentmods badge for opgg-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/opgginc/opgg-mcp/agents-md.svg)](https://agentmods.dev/instructions/opgginc/opgg-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/opgginc/opgg-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/opgginc/opgg-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 974 This file is loaded in full into every session.
When invoked 974 The same file — it is already loaded in full.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00974 $0.00974
Opus 5 $0.00487 $0.00487
Sonnet 5 $0.00195 $0.00195
Haiku 4.5 $0.00097 $0.00097

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

Security

Grade A, and why

opgg-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 8d 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.

AGENTS.md · 56 lines

How it starts

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

AGENTS.md

This repo is a thin stdio→HTTP proxy for the remote OP.GG MCP server. Tool definitions live on the remote endpoint, not in this repo. See README.md for the user-facing tool list.

Project Map

  • src/index.ts: entry point. Connects to the remote MCP endpoint and binds it to stdio.
  • src/proxy-server.ts: generic capability bridge (tools, resources, prompts, logging, completion).
  • dist/: build output from tsup. Git-ignored. Do not edit.
  • docs/apps-sdk/, docs/kakao/: reference material only. Not part of the build.
  • Dockerfile, smithery.yaml: Smithery deployment artifacts. Dockerfile is generated by Smithery.
  • README.md, README.ko.md, README.ja.md, README.zh-CN.md, README.zh-TW.md, README.pt-BR.md: keep the 6 language READMEs in sync.

Commands

  • Install: pnpm install.
  • Build: pnpm build (runs tsup; emits ESM + .d.ts + sourcemap to dist/).
  • Type check: pnpm exec tsc --noEmit.
  • Run locally: node dist/index.js (requires pnpm build first).
  • Smoke test with MCP Inspector: pnpm test. Requires dist/index.js to exist.

Workflow Rules

  • Use pnpm. Do not use npm or yarn. The lockfile is pnpm-lock.yaml.
  • Use Node 22 features. tsconfig.json extends @tsconfig/node22.
  • Use ESM only. package.json declares "type": "module" and tsup.format is ["esm"].
  • The remote endpoint https://mcp-api.op.gg/mcp is hardcoded in src/index.ts. Do not change it without coordinating with the OP.GG MCP service owners.
  • Do not declare MCP tools, resources, or prompts in this repo. The proxy forwards them from the remote server. Adding local definitions defeats the proxy and breaks parity with the remote.
  • When the remote tool list changes, update all 6 README files together. The last sync commit was 3deb793 docs: update tool list to match latest MCP server.
  • Do not edit Dockerfile to add app logic. The header says Generated by https://smithery.ai; regenerate via Smithery if the build pipeline changes.
  • Do not commit dist/, node_modules/, or .env. See .gitignore.

Read the full file on GitHub · 56 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. 8d ago First seen · 56 lines · 974 tokens per session scan A fe4e4d241854

Subscribe to this mod's changes

opgg-mcp AGENTS.md is an instructions file published in the GitHub repository opgginc/opgg-mcp (102 stars, last pushed 1mo ago), licensed MIT. It adds 974 tokens to every session, about $0.0049 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.

Related

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.

vercel/next.js · 7,296 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,153 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

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

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,469 tokens

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