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/flight505/mcp_dincoder/copilot-instructionsgit clone --depth 1 https://github.com/flight505/MCP_DinCoderWhat 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.00749 | $0.00749 |
| Opus 5 | $0.00375 | $0.00375 |
| Sonnet 5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
MCP_DinCoder 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DinCoder Spec-Driven Development
This project uses DinCoder for spec-driven development workflows.
MCP Tools Available
The DinCoder MCP server provides tools for structured development:
Project Initialization
specify_start- Initialize .dincoder/ directoryprereqs_check- Verify environment setup
Specification Phase
specify_describe- Create detailed specificationspec_validate- Check specification qualityspec_refine- Update specific sectionsclarify_add/resolve/list- Manage clarifications
Planning Phase
plan_create- Generate technical implementation planartifacts_analyze- Verify spec-plan alignment
Task Management
tasks_generate- Create actionable task listtasks_visualize- Show dependency graphs (Mermaid/Graphviz/ASCII)tasks_filter- Smart filtering (next, frontend, backend, ready, cleanup)tasks_search- Fuzzy search across taskstasks_stats- Progress analytics and chartstasks_tick- Mark single task completetasks_tick_range- Batch completion (T001-T005 syntax)
Workflow
-
Specify - Define what to build
- Run
specify_startto initialize - Run
specify_describeto create spec.md - Run
spec_validateto ensure quality
- Run
-
Plan - Design how to build it
- Run
plan_createto generate plan.md - Run
artifacts_analyzeto verify alignment
- Run
-
Execute - Build following tasks
- Run
tasks_generateto create tasks.md - Run
tasks_filterwith preset "next" to see actionable items - Mark complete with
tasks_tickortasks_tick_range
- Run
-
Track - Monitor progress
- Run
tasks_statsfor progress analytics - Run
tasks_visualizefor dependency graphs
- Run
MCP Prompts (Slash Commands)
Use these slash commands in Copilot Chat (agent mode):
/mcp.dincoder.start_project- Initialize new project/mcp.dincoder.create_spec- Create specification/mcp.dincoder.generate_plan- Generate implementation plan/mcp.dincoder.create_tasks- Generate task list/mcp.dincoder.review_progress- View progress report/mcp.dincoder.validate_spec- Check spec quality/mcp.dincoder.next_tasks- Show next actionable tasks
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 · 98 lines · 749 tokens per session scan A 968979068881
MCP_DinCoder copilot-instructions.md is an instructions file published in the GitHub repository flight505/MCP_DinCoder (2 stars, last pushed 10mo ago), licensed MIT. It adds 749 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
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.
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).
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.