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/duplocloud/mcp/copilot-instructionsgit clone --depth 1 https://github.com/duplocloud/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/duplocloud/mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/duplocloud/mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/duplocloud/mcp/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.00737 | $0.00737 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
mcp 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 2d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for the DuploCloud MCP Server
This document provides instructions for GitHub Copilot to effectively assist with development in this repository.
Project Overview
This project is a FastMCP server that acts as a wrapper for the duplocloud-client Python package (which powers duploctl). Its primary goal is to dynamically expose duploctl commands as MCP (Model-Context-Protocol) tools and resources. This allows AI agents and other MCP-compatible clients to interact with the DuploCloud platform programmatically.
The core logic for this wrapping and registration is in duplocloud/mcp/server.py.
Key Concepts & Architecture
1. Dynamic duploctl Command Registration
The central feature of this server is its ability to dynamically discover and register duploctl commands.
- Source of Commands: Commands are defined in the
duplocloud-clientlibrary using the@Commanddecorator. - Discovery Mechanism: The server uses the
schemaobject fromduplocloud.commanderto get a registry of all available commands. - Registration Logic: The
_register_resource_commandsmethod induplocloud/mcp/server.pyiterates through this schema and registers each command as an MCP tool. Read-only operations are also marked for registration as MCP resources.
2. Important duplocloud-client Modules
When working on this project, you will frequently need to reference the source code of the duplocloud-client package. It is installed in the virtual environment.
- Path:
/workspaces/mcp/.venv/lib/python3.13/site-packages/duplocloud/ commander.py: This file is critical. It contains the@Commandand@Resourcedecorators and maintains theschemadictionary, which is the source of truth for all registered commands.client.py: This is the main entry point for theduplocloud-client. TheDuploClientclass handles configuration, authentication, and loading resources. The MCP server instantiates this client to execute commands.
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.
- 2d ago First seen · 46 lines · 737 tokens per session scan A 1bd1c2ffe587
mcp copilot-instructions.md is an instructions file published in the GitHub repository duplocloud/mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 737 tokens to every session, about $0.0037 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.