MCP_DinCoder CLAUDE.md

A set of instructions for an AI agent working on MCP_DinCoder, a server that helps organize software development around written specifications. It explains the project, its requirements, and how AI-discovered workflow prompts should work.

In plain words
What is it for?
It is for building or maintaining the MCP_DinCoder server, including its HTTP connection, TypeScript setup, and specification-driven workflows such as defining a project, planning it, and creating tasks.
Why use it?
It gives the agent the repository rules and the intended behavior of its prompts, reducing guesswork during development. MCP is a standard way for AI agents to connect to tools and services.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/flight505/mcp_dincoder/claude-md
Clone the repo
git clone --depth 1 https://github.com/flight505/MCP_DinCoder
Per session 1,557 This file is loaded in full into every session.
When invoked 1,557 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01557 $0.01557
Opus 5 $0.00779 $0.00779
Sonnet 5 $0.00311 $0.00311
Haiku 4.5 $0.00156 $0.00156

Measured 2d ago against content hash 4be703b0ed9b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

MCP_DinCoder CLAUDE.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.

CLAUDE.md · 182 lines

How it starts

The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to AI agents when working with code in this repository.

Project Overview

Spec-Driven MCP Orchestrator - Model Context Protocol server with Streamable HTTP transport, exposing Spec Kit tools (specify, plan, tasks) for AI-assisted spec-driven development workflows.

Critical Requirements

  • Protocol: MCP Streamable HTTP (Protocol Revision 2025-03-26)
  • TypeScript SDK: @modelcontextprotocol/sdk v1.17.5+
  • Node.js: >=20
  • Transport: HTTP only (STDIO deprecated Sept 7, 2025)
  • TypeScript Config: MUST use module/moduleResolution: "NodeNext"

⚠️ MCP Prompts - CRITICAL UNDERSTANDING

MCP prompts are workflow orchestrators for AI agents, NOT user-typed commands.

How They Work

  1. AI Discovery: Agents discover prompts via prompts/list JSON-RPC call
  2. AI Invocation: Agents call prompts/get programmatically when relevant
  3. User Experience: Users describe goals in natural language; AI uses appropriate prompt automatically

Example

User: "Let's start a new project called task-manager"

Behind the scenes:

  • AI recognizes this matches start_project prompt
  • AI invokes prompt programmatically
  • AI receives workflow instructions
  • AI guides user through setup

User sees: Natural conversation (NOT a slash command)

Platform Behavior

  • Claude Code: @ = files, / = native commands, MCP prompts = invisible
  • VS Code/Copilot/Cursor: MCP prompts integrated into agent workflows

Registered Prompts (v0.4.0+)

Prompt Purpose Arguments
start_project Initialize new project projectName, agent (optional)
create_spec Create specification description
generate_plan Generate implementation plan specPath (optional)
create_tasks Break down into tasks planPath (optional)
review_progress Generate progress report None
validate_spec Check specification quality specPath (optional)
next_tasks Show actionable tasks limit (optional)

Read the full file on GitHub · 182 lines

Changes

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.

  1. 2d ago First seen · 182 lines · 1,557 tokens per session scan A 4be703b0ed9b

Subscribe to this mod's changes

MCP_DinCoder CLAUDE.md is an instructions file published in the GitHub repository flight505/MCP_DinCoder (2 stars, last pushed 10mo ago), licensed MIT. It adds 1,557 tokens to every session, about $0.0078 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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens