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/major/pcp-mcp/agents-mdgit clone --depth 1 https://github.com/major/pcp-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/major/pcp-mcp/agents-md)<a href="https://agentmods.dev/instructions/major/pcp-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/major/pcp-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 | $0.01278 | $0.01278 |
| Opus 5 | $0.00639 | $0.00639 |
| Sonnet 5 | $0.00256 | $0.00256 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
pcp-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROJECT KNOWLEDGE BASE
Generated: 2026-01-18 Commit: bb3250e Branch: main
OVERVIEW
MCP server for Performance Co-Pilot (PCP) metrics. Exposes system performance data (CPU, memory, disk, network, processes) via Model Context Protocol tools and resources. Built on FastMCP 3.1+ with httpx async client for pmproxy REST API.
STRUCTURE
pcp-mcp/
├── src/pcp_mcp/ # Core package (see src/pcp_mcp/AGENTS.md)
│ ├── tools/ # MCP tools (see src/pcp_mcp/tools/AGENTS.md)
│ ├── utils/ # Extractors, builders
│ └── prompts/ # LLM system prompts
├── tests/ # Test suite (see tests/AGENTS.md)
├── docs/ # MkDocs source
└── site/ # Generated docs (gitignored)
See subdirectory AGENTS.md files for detailed guidance on each module.
WHERE TO LOOK
| Task | Location |
|---|---|
| Add new tool | src/pcp_mcp/tools/ |
| Modify HTTP client | src/pcp_mcp/client.py |
| Change config | src/pcp_mcp/config.py |
| Add response model | src/pcp_mcp/models.py |
| Map exceptions | src/pcp_mcp/errors.py |
| CLI changes | src/pcp_mcp/__init__.py |
| Server setup | src/pcp_mcp/server.py |
CONVENTIONS
Code Style
- Line length: 100 chars
- Docstrings: Google-style (enforced by ruff D rules)
- Imports:
from __future__ import annotationsat top - Async: Default for I/O operations
Ruff Rules
E, F, I, UP, B, SIM, ASYNC, D — tests exempt from D rules
Type Checking
- Tool: ty (not pyright, not mypy)
- Target: Python 3.14
- Mode: standard
Environment Variables
All prefixed with PCP_:
PCP_HOST,PCP_PORT— pmproxy connectionPCP_TARGET_HOST— remote pmcd hostPCP_USE_TLS,PCP_TIMEOUT— connection optionsPCP_USERNAME,PCP_PASSWORD— auth (optional)
ANTI-PATTERNS
Counter Metrics (CRITICAL)
These are CUMULATIVE (since boot), NOT per-second rates:
kernel.all.cpu.*disk.all.read_bytes,disk.all.write_bytesnetwork.interface.in.bytes,network.interface.out.bytesproc.psinfo.utime,proc.psinfo.stime
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.
- 3d ago First seen · 144 lines · 1,278 tokens per session scan A 02e54def693f
pcp-mcp AGENTS.md is an instructions file published in the GitHub repository major/pcp-mcp (0 stars, last pushed 10d ago), licensed MIT. It adds 1,278 tokens to every session, about $0.0064 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.