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/carldog/plex-mcp/agents-mdgit clone --depth 1 https://github.com/CarlDog/plex-mcpWhat 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 | $0.01995 | $0.01995 |
| Opus 5 | $0.00997 | $0.00997 |
| Sonnet 5 | $0.00399 | $0.00399 |
| Haiku 4.5 | $0.00199 | $0.00199 |
Grade A, and why
plex-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- plex-mcp CLAUDE.md — 86% identical, 51 lines differ
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plex-mcp
MCP server for Plex Media Server, packaged as a Docker container.
Fleet standards: ts-mcp-server v1.0 — audited 2026-07-25
Status
Single source of truth: STATUS.md. Do not duplicate status into this file, MEMORY.md, or Serena memories — reference STATUS.md.
Current Sprint
See STATUS.md for the active phase, what's done, and what's next.
Stack
- TypeScript (Node 22+, ESM,
NodeNextmodule resolution) @modelcontextprotocol/sdk(high-levelMcpServerAPI)zodfor tool input schemas- Plex HTTP API via
fetch(no Plex SDK dependency) - Docker multi-stage build (alpine, non-root)
Layout
src/index.ts— MCP server entry. Decides transport based onMCP_PORT.src/mcp-route.ts— the Streamable HTTP/mcproute: Host/Origin allowlist, per-session transport map, idle sweep, session dispatch. Split out ofindex.tsso it can be imported by a test —index.tsself-executes on import, so nothing in it was reachable without booting a server. Covered bytests/mcp-route.test.ts.src/plex.ts— Plex HTTP API client.src/tautulli.ts— optional direct Tautulli HTTP client, fail-soft config, normalized privacy-allowlisted response types.src/log.ts— small structured logger (stderr, level-gated viaLOG_LEVELenv var). See README for format and levels.src/tools/— tool registrations split per domain (discovery.ts,sessions.ts,playback.ts,playlists.ts,hubs.ts,admin.ts,images.ts,diagnostics.ts,tautulli.ts).index.tsorchestrates viaregisterTools(server, plex, tautulli);helpers.tsholds shared utilities (asText,withLogging).Dockerfile— multi-stage build for the runtime image.docker-compose.yml— Compose/Portainer deployment using HTTP transport.docs/PLEX-API.md— curated reference for the Plex HTTP API: external doc links, gotchas we've hit (pagination pairing,/:/scrobbleempty responses,typeinteger codes), and rough endpoint shapes for capabilities we haven't built yet. Read this before adding new tools.docs/CHATGPT-APPS-SDK.md— future-work spec for making plex-mcp consumable from a ChatGPT account (OAuth 2.1 protected-resource setup, tool annotation hints, optional UI widgets, infrastructure choices). Not started; phased plan inside..githooks/pre-commit— gitleaks + PII pattern scan..gitleaks.toml— secret-scanning config.
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 · 171 lines · 1,995 tokens per session scan A a5991492533d
plex-mcp AGENTS.md is an instructions file published in the GitHub repository CarlDog/plex-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 1,995 tokens to every session, about $0.0100 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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.