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/mediagraph-io/mediagraph-mcp/agents-mdgit clone --depth 1 https://github.com/mediagraph-io/mediagraph-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/mediagraph-io/mediagraph-mcp/agents-md)<a href="https://agentmods.dev/instructions/mediagraph-io/mediagraph-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/mediagraph-io/mediagraph-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.01455 | $0.01455 |
| Opus 5 | $0.00727 | $0.00727 |
| Sonnet 5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
mediagraph-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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mediagraph-mcp CLAUDE.md — 91% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex when working with this repository.
Project Overview
Mediagraph MCP is a Model Context Protocol (MCP) server that provides AI assistants with access to the Mediagraph digital asset management API. It enables Codex and other MCP-compatible AI assistants to search, manage, and organize media assets.
Tech Stack:
- TypeScript with ESM modules
- Node.js 20+
- MCP SDK (
@modelcontextprotocol/sdk) - OAuth 2.0 with PKCE for authentication
- Vitest for testing
- tsup for bundling
Common Commands
# Install dependencies
npm install
# Build the project
npm run build
# Run in development mode (watch)
npm run dev
# Run tests
npm test
# Run tests in watch mode
npm run test:watch
# Type check without emitting
npm run typecheck
# Start the MCP server
npm start
Project Structure
src/
├── index.ts # MCP server entry point, CLI handling
├── api/
│ ├── client.ts # Mediagraph API client (all HTTP methods)
│ ├── types.ts # Re-exports from types/
│ └── types/ # Split type definitions by domain
│ ├── index.ts # Re-exports all types
│ ├── assets.ts # Asset, SearchParams, etc.
│ ├── groups.ts # Collection, Lightbox, StorageFolder
│ ├── tags.ts # Tag, Taxonomy, etc.
│ ├── users.ts # User, Organization, Membership
│ └── ... # Other domain types
├── auth/
│ ├── oauth.ts # OAuth flow with PKCE support
│ └── token-store.ts # Encrypted token storage
├── tools/ # MCP tool definitions and handlers
│ ├── index.ts # Combines all tool modules
│ ├── shared.ts # Common types and helpers
│ ├── assets.ts # Asset tools (search, get, update, etc.)
│ ├── groups.ts # Collection, Lightbox, StorageFolder tools
│ ├── tags.ts # Tag, Taxonomy tools
│ ├── admin.ts # User groups, invites, uploads, etc.
│ └── ... # Other tool modules
├── resources/ # MCP resource providers
│ └── index.ts # mediagraph:// URI handlers
└── __tests__/ # Test files
├── tools.test.ts
├── types.test.ts
└── client.test.ts
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.
- 4d ago First seen · 187 lines · 1,455 tokens per session scan A 92c7d40b28a0
mediagraph-mcp AGENTS.md is an instructions file published in the GitHub repository mediagraph-io/mediagraph-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,455 tokens to every session, about $0.0073 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
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).
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.
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).