Borrowing it
Nothing to install: this file belongs to Albenzoo/Mockoon-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Albenzoo/Mockoon-mcp/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/Albenzoo/Mockoon-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/albenzoo/mockoon-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/albenzoo/mockoon-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/albenzoo/mockoon-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.1 | $0.02083 | $0.02083 |
| Opus 5 | $0.01042 | $0.01042 |
| Sonnet 5 | $0.00417 | $0.00417 |
| Haiku 4.5 | $0.00208 | $0.00208 |
Grade A, and why
Mockoon-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 6d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — mockoon-mcp-server
Commands
npm run build # compile TypeScript → dist/
npm run dev # run src/index.ts directly with tsx (no build required)
npm start # run dist/index.js (requires build)
No automated tests. To manually verify the MCP server responds correctly:
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}' | node dist/index.js
Key dependencies
| Package | Version | Notes |
|---|---|---|
@modelcontextprotocol/sdk |
^1.27.1 | MCP server + stdio transport |
@mockoon/commons |
^9.5.0 | Environment, Route, DataBucket, enums |
zod |
^4.3.6 | Zod v4 — some APIs differ from v3 |
typescript |
^5.9.3 | target ES2022, moduleResolution Node16 |
tsx |
^4.21.0 | dev runner (no build required) |
Architecture
This is an MCP server (Model Context Protocol) that exposes AI tools to control Mockoon. It communicates via stdio (JSON-RPC 2.0) — it does not expose any HTTP port of its own.
src/index.ts ← entry point: creates McpServer, registers server tools
(start_server, stop_server, list_running_servers),
imports and calls all registerXxxTools(), connects StdioServerTransport
src/tools/environments.ts ← tools: list_environments, create_environment, delete_environment
src/tools/routes.ts ← tools: list_routes, get_route, create_route, create_route_with_responses,
bulk_create_routes, update_route, duplicate_route, delete_route,
add_route_response, set_default_response, get_default_response
src/tools/templates.ts ← tools: list_templates, create_template, update_template, delete_template
src/mockoon/fileManager.ts ← reads/writes Mockoon JSON files on disk
src/mockoon/processManager.ts ← starts/stops mockoon-cli processes (in-memory Map<environmentId, ChildProcess>)
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.
- 6d ago First seen · 198 lines · 2,083 tokens per session scan A 3c0e2e3c2814
Mockoon-mcp copilot-instructions.md is an instructions file published in the GitHub repository Albenzoo/Mockoon-mcp (3 stars, last pushed 4mo ago), licensed MIT. It adds 2,083 tokens to every session, about $0.0104 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.