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/kieutrongthien/coding-mcp/copilot-instructionsgit clone --depth 1 https://github.com/kieutrongthien/coding-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/kieutrongthien/coding-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/kieutrongthien/coding-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kieutrongthien/coding-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.00320 | $0.00320 |
| Opus 5 | $0.00160 | $0.00160 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
coding-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 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
Copilot Instructions for coding-mcp
These instructions apply to all coding agents working in this repository.
Mission
Build and maintain a production-grade MCP server for multi-project coding workflows with strong safety controls.
Architecture Rules
- Preserve modular boundaries: config, core, services, and mcp layers.
- Reuse shared services via bootstrap container; do not bypass service abstractions in tool handlers.
- Keep STDIO and HTTP transports behaviorally consistent.
Safety Rules (Mandatory)
- Never allow path traversal outside project roots.
- Keep destructive operations guarded by explicit confirmation flags.
- Keep command execution allowlist-based; do not introduce shell concatenation.
- Prefer
spawn(command, args, { shell: false })patterns. - Maintain output/file size limits and timeout controls.
MCP Contract Rules
- Keep zod schemas in sync with tool/resource/prompt handlers.
- Keep response envelopes consistent (
ok,operation,data,warnings,errors). - Return structured failures with clear error codes and details.
Testing Rules
Before proposing completion for code changes:
- Run
npm run typecheck - Run
npm test - Add or update tests for changed behavior
Documentation Rules
- Update README and env examples when changing CLI/config behavior.
- Update GitHub templates/workflows when project process changes.
Preferred Workflow
- Read affected schemas and service interfaces first.
- Implement minimal changes preserving existing API contracts.
- Validate with typecheck/tests.
- Summarize changes with impacted files and behavior deltas.
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 · 48 lines · 320 tokens per session scan A 048a0c2bd8c1
coding-mcp copilot-instructions.md is an instructions file published in the GitHub repository kieutrongthien/coding-mcp (2 stars, last pushed 5mo ago), licensed MIT. It adds 320 tokens to every session, about $0.0016 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
zot AGENTS.md
AGENTS.md instructions for patriceckhart/zot, covering working agreement for zot, product intent, starting a task, code ownership map and correctness contracts.
code-assistant AGENTS.md
AGENTS.md instructions for stippi/code-assistant, covering repository guidance, essential commands, building and development, testing specific components and architecture overview.
talkcody AGENTS.md
Instructions for talkcody/talkcody, covering project development guide for ai agents, project overview, architecture diagram, technology stack and frontend.
vix AGENTS.md
AGENTS.md instructions for get-vix/vix, covering agents.md, project overview, architecture, instance control channel and development commands.
ZenCODE AGENTS.md
AGENTS.md instructions for gerardogrisolini/ZenCODE, covering agents.md, project, architecture map, build and validation and linux validation.
flyto-ai AGENTS.md
AGENTS.md instructions for flytohub/flyto-ai, covering flyto-ai agent rules, coding route rules, architecture invariant: flytohub product topology, flyto2 project memory contract and flyto2 frontend quality gate.