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/albertik322-sudo/mcp-control-plane/agents-mdgit clone --depth 1 https://github.com/albertik322-sudo/mcp-control-planeWrote 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/albertik322-sudo/mcp-control-plane/agents-md)<a href="https://agentmods.dev/instructions/albertik322-sudo/mcp-control-plane/agents-md"><img src="https://agentmods.dev/badge/instructions/albertik322-sudo/mcp-control-plane/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.00163 | $0.00163 |
| Opus 5 | $0.00081 | $0.00081 |
| Sonnet 5 | $0.00033 | $0.00033 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
mcp-control-plane 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 an MCP control plane. Begin with Context Store orientation and prefer the relevant MCP server over ad-hoc infrastructure shell commands.
Safe workflow
- Use
codex_memoryfor project and tool capability context. - Use read-only health, audit, and snapshot tools before mutations.
- Keep remote changes narrow, reversible, and explicitly authorized.
- Never print or store secret values.
- Preserve authorization checks inside MCP/API implementations.
- Run offline tests, the control-plane audit, and stateless conformance after MCP runtime changes.
- Restart long-lived MCP processes after code or dependency changes.
Do not commit .env, runtime state, infrastructure snapshots, captures,
firmware, generated artifacts, vendored tools, or private operational data.
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 · 19 lines · 163 tokens per session scan A 2b65ac37f90a
mcp-control-plane AGENTS.md is an instructions file published in the GitHub repository albertik322-sudo/mcp-control-plane (2 stars, last pushed 3d ago), licensed MIT. It adds 163 tokens to every session, about $0.0008 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
selfhost-ai CLAUDE.md
Claude Code instructions for kossakovsky/selfhost-ai, covering claude.md, project overview, core architecture, key files and installation flow.
homelab-monitor CLAUDE.md
Claude Code instructions for SikamikanikoBG/homelab-monitor, covering claude.md and conventions.
piper CLAUDE.md
Claude Code instructions for piperbox/piper, covering claude.md, what this is, coding principles, 1. think before coding and 2. simplicity first.
homelab-mcp CLAUDE.md
Instructions for bjeans/homelab-mcp, covering claude development guide for homelab mcp, project overview, core philosophy, project structure and architecture patterns.
piper AGENTS.md
AGENTS.md instructions for piperbox/piper: Read CLAUDE.md in full first — it is the authoritative source for coding principles, commands, constraints, layering, and branch/PR/issue workflow. This file only captures high-signal facts an agent would otherwise get wrong that aren't obvious from filenames or CLAUDE.md.
fengarde CLAUDE.md
Claude Code instructions for supermhel/fengarde, covering claude.md, what this is, commands, targeted suites (see runalltests.sh for the full list) and docker stack (full live pipeline).