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/tosin2013/documcp/copilot-instructionsgit clone --depth 1 https://github.com/tosin2013/documcpWrote 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/tosin2013/documcp/copilot-instructions)<a href="https://agentmods.dev/instructions/tosin2013/documcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/tosin2013/documcp/copilot-instructions.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.01894 | $0.01894 |
| Opus 5 | $0.00947 | $0.00947 |
| Sonnet 5 | $0.00379 | $0.00379 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
documcp 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 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DocuMCP AI Coding Agent Instructions
DocuMCP is an intelligent MCP server for GitHub Pages documentation deployment with 45+ tools, Knowledge Graph memory system, and AST-based code analysis.
Architecture Essentials
MCP Server Design (src/index.ts)
- Stateless operation: Each tool analyzes current state; no persistent session data
- Resource storage: Temporary session context in
resourceStoreMap with URIs likedocumcp://analysis/{id} - Response format: ALL tools MUST use
formatMCPResponse()fromsrc/types/api.tsreturningMCPToolResponse - Memory integration: Tools auto-store results in JSONL (
.documcp/memory/) and query historical data
Tool Implementation Pattern
Every tool follows this structure:
- Zod schema for input validation (e.g.,
inputSchema.parse()) - Business logic with error handling
- Return via
formatMCPResponse({ success, data, metadata, recommendations?, nextSteps? }) - Store result as resource:
storeResourceFromToolResult(result, 'analysis', analysis.id)
Example (see src/tools/analyze-repository.ts):
const inputSchema = z.object({
path: z.string(),
depth: z.enum(["quick", "standard", "deep"]).optional(),
});
export async function analyzeRepository(
args: unknown,
): Promise<MCPToolResponse> {
const input = inputSchema.parse(args);
// ... logic ...
return formatMCPResponse({
success: true,
data: analysis,
metadata: { toolVersion, executionTime, timestamp },
});
}
Knowledge Graph Memory (src/memory/)
- Entities: Project, User, Configuration, Technology, CodeFile, DocumentationSection (see
src/memory/schemas.ts) - Relationships:
project_uses_technology,project_deployed_with,similar_to,documents, etc. - Storage:
.documcp/memory/knowledge-graph-entities.jsonlandknowledge-graph-relationships.jsonl - Integration: Use
createOrUpdateProject(),getProjectContext(),trackDeployment()fromsrc/memory/kg-integration.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 · 209 lines · 1,894 tokens per session scan A c0823797286e
documcp copilot-instructions.md is an instructions file published in the GitHub repository tosin2013/documcp (9 stars, last pushed 1mo ago), licensed MIT. It adds 1,894 tokens to every session, about $0.0095 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
Skill_Seekers CLAUDE.md
Instructions for yusufkaraaslan/Skill_Seekers, covering claude.md, project overview, essential commands, required before running tests or cli (src/ layout) and run all tests (never skip - all must pass before commits).
alcove AGENTS.md
AGENTS.md instructions for epicsagas/alcove, covering claude.md, repository purpose, actual location, structure and karpathy 3-layer architecture.
calc-mcp CLAUDE.md
Claude Code instructions for coo-quack/calc-mcp, covering project rules, tech stack, commands, project structure and tool architecture.
pfsense-mcp-server AGENTS.md
AGENTS.md instructions for night4me/pfsense-mcp-server, covering pfsense mcp server, architecture and security, development workflow, long-running validation and test parallelism.
Noema AGENTS.md
Instructions for Fail-Safe/Noema, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
video-research-mcp AGENTS.md
Instructions for Galbaz1/video-research-mcp, covering agents.md, scope, what this is, commands and code review trigger protocol.