wsdot-mcp-server: Instructions file for Claude Code

CLAUDE.md

wsdot-mcp-server CLAUDE.md is an instructions file for Claude Code from cyanheads/wsdot-mcp-server. It costs 5,320 tokens per session, scanned A, a copy of obsidian-mcp-server AGENTS.md, Apache-2.0.

A set of project instructions for developing the cyanheads MCP server, including its runtime versions, coding rules, error handling, logging, storage, secrets, and user-input patterns. MCP is a standard way for AI clients to call server-provided tools and resources.

In plain words
What is it for?
Use it when adding or modifying handlers, handling errors, logging requests, accessing tenant-scoped storage, requesting missing input, and checking whether work is complete.
Why use it?
It gives contributors one reference for the server's expected conventions, reducing inconsistent implementations and mistakes during changes.

Instructions file for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is cyanheads/wsdot-mcp-server's own configuration. It tells Claude Code how to work on wsdot-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything wsdot-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to cyanheads/wsdot-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/cyanheads/wsdot-mcp-server/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/cyanheads/wsdot-mcp-server

Made for: Claude Code.

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

agentmods badge for wsdot-mcp-server CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cyanheads/wsdot-mcp-server/claude-md.svg)](https://agentmods.dev/instructions/cyanheads/wsdot-mcp-server/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/cyanheads/wsdot-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/wsdot-mcp-server/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 5,320 This file is loaded in full into every session.
When invoked 5,320 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 78% copy Near-identical to another mod 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.1 $0.05320 $0.05320
Opus 5 $0.02660 $0.02660
Sonnet 5 $0.01064 $0.01064
Haiku 4.5 $0.00532 $0.00532

Measured 6d ago against content hash d3c6b851e6bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

wsdot-mcp-server 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 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.

Origin

This is a copy

78% identical to obsidian-mcp-server AGENTS.md — 296 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 335 lines

How it starts

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

Developer Protocol

Server: @cyanheads/wsdot-mcp-server Version: 0.2.5 Framework: @cyanheads/mcp-ts-core ^0.12.3 Engines: Bun ≥1.3.0, Node ≥24.0.0 MCP SDK: @modelcontextprotocol/server ^2.0.0 (protocol revisions 2026-07-28 and 2025-*) Zod: ^4.4.3

Read the framework docs first: node_modules/@cyanheads/mcp-ts-core/CLAUDE.md contains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.


Core Rules

  • Logic throws, framework catches. Tool/resource handlers are pure — throw on failure, no try/catch. Plain Error is fine; the framework catches, classifies, and formats. Use error factories (notFound(), validationError(), etc.) when the error code matters.
  • Use ctx.log for request-scoped logging. No console calls.
  • Use ctx.state for tenant-scoped storage. Never access persistence directly.
  • Need input the caller didn't supply? return ctx.requestInput(...) and read ctx.inputs when the handler is re-entered. Never await for user input mid-handler.
  • Secrets in env vars only — never hardcoded.
  • Close the loop on issues. When implementing work tracked by a GitHub issue, comment on the issue with what landed and close it. Do both — a comment without a close leaves stale issues open; a close without a comment leaves no record of what shipped. The comment is for future readers — state the concrete changes, not the conversation that produced them.

Patterns

Tool

import { tool, z } from '@cyanheads/mcp-ts-core';
import { getTrafficApiService } from '@/services/traffic/traffic-service.js';

export const getMountainPasses = tool('wsdot_get_mountain_passes', {
  description: 'Returns current road conditions for all Washington State mountain passes.',
  annotations: { readOnlyHint: true },
  input: z.object({}),
  output: z.object({
    passes: z.array(z.object({
      passName: z.string().optional().describe('Name of the mountain pass.'),
      roadCondition: z.string().optional().describe('Current road condition.'),
    })).describe('Current conditions for all WA mountain passes.'),
  }),

  async handler(input, ctx) {
    const svc = getTrafficApiService();
    const passes = await svc.getMountainPassConditions();
    ctx.log.info('Mountain passes fetched', { count: passes.length });
    return { passes };
  },

  // format() populates content[] — the markdown twin of structuredContent.
  // Different clients read different surfaces (Claude Code → structuredContent,
  // Claude Desktop → content[]); both must carry the same data.
  // Enforced at lint time: every field in `output` must appear in the rendered text.
  format: (result) => [{
    type: 'text',
    text: result.passes.map(p => `**${p.passName}**: ${p.roadCondition}`).join('\n'),
  }],
});

Read the full file on GitHub · 335 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. 6d ago First seen · 335 lines · 5,320 tokens per session scan A d3c6b851e6bf

Subscribe to this mod's changes

wsdot-mcp-server CLAUDE.md is an instructions file published in the GitHub repository cyanheads/wsdot-mcp-server (1 stars, last pushed 12d ago), licensed Apache-2.0. It adds 5,320 tokens to every session, about $0.0266 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to obsidian-mcp-server AGENTS.md, differing in 296 lines, and is treated as a copy.

Related

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.

vercel/next.js · 7,296 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

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

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

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,469 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