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/dans-plugins/dpc-mcp-server/copilot-instructionsgit clone --depth 1 https://github.com/Dans-Plugins/dpc-mcp-serverWhat 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.00577 | $0.00577 |
| Opus 5 | $0.00289 | $0.00289 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
dpc-mcp-server copilot-instructions.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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot instructions
This repository follows the DPC (Dans Plugins Community) conventions defined at https://github.com/Dans-Plugins/dpc-conventions.
What this is
An MCP (Model Context Protocol) server that serves the DPC Zettelkasten — a knowledge base about the DPC Minecraft plugins where every claim cites a file in a Dans-Plugins repository, pinned at a commit SHA.
Node 18+, CommonJS, no build step.
Two hard rules
No runtime dependencies. MCP's stdio transport is implemented directly in
src/protocol.js (JSON-RPC 2.0, newline-delimited). Do not add a runtime
dependency, including the official SDK — it is a dev dependency used by the
tests to drive this server as a real client would.
The GraphQL schema is not maintained here. vendor/zk-graphql.js and
vendor/dataset.json are generated copies from the zettelkasten, refreshed by
npm run sync. Schema changes belong in that repository's lib/zk-graphql.js.
Editing vendor/ directly is reverted by the next sync.
Layout
src/protocol.js— the transport. Change with care; the live-client tests are what prove it still works.src/tools.js— tools, their descriptions, and their handlers.src/server.js— data loading, resources, wiring.tools/sync.js— refreshesvendor/, and refuses a snapshot whose engine and data disagree.test/run.js— data, raw-protocol, and live-client layers.
Conventions that matter here
stdout is the protocol. Every human-facing message goes to stderr. A single
stray line on stdout desynchronises the client. Never console.log in src/.
Tool descriptions say when to use the tool, not just what it does. They are the only documentation the model receives.
Tool failures return text(message, true), not a thrown exception, so the
model sees isError and can recover. Throw only for malformed calls.
Nothing is written and nothing is fetched at request time. The graph is read once at startup. The server has no write path; keep it that way.
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 · 60 lines · 577 tokens per session scan A bafaffdde5ec
dpc-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository Dans-Plugins/dpc-mcp-server (0 stars, last pushed 4d ago), licensed MIT. It adds 577 tokens to every session, about $0.0029 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
obsidian-mcp-server AGENTS.md
Instructions for cyanheads/obsidian-mcp-server, covering agent protocol, what's next?, core rules, patterns and tool — obsidianlisttags.
mcp-documentation-server copilot-instructions.md
Instructions for andrea9293/mcp-documentation-server, covering mcp documentation server - ai coding agent instructions, architecture overview, core components, server entry point (src/server.ts) and embedding providers (src/embedding-provider.ts).
data-olympus AGENTS.md
Instructions for knaisoma/data-olympus, covering data olympus, project overview, architecture, development workflow and code standards.
grounded-knowledge-engine AGENTS.md
Instructions for dimosgit/grounded-knowledge-engine, covering agent guide, agent operating contract, authorship and attribution, two npm trees and commands — engine (repo root).
data-olympus copilot-instructions.md
Instructions for knaisoma/data-olympus: Read and follow all instructions in AGENTS.md. Read and follow all rules in .rules/. Read and follow the global Codex and Claude Code collaboration rule in /kn-projects/company-knowledge/tooling/codex-claude-collaboration.md.
data-olympus CLAUDE.md
Instructions for knaisoma/data-olympus: Read and follow all instructions in AGENTS.md. Read and follow all rules in .rules/. Read and follow the global Codex and Claude Code collaboration rule in /kn-projects/company-knowledge/tooling/codex-claude-collaboration.md.