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/razdo227/web-dev-mcp/claude-mdgit clone --depth 1 https://github.com/razdo227/web-dev-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/razdo227/web-dev-mcp/claude-md)<a href="https://agentmods.dev/instructions/razdo227/web-dev-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/razdo227/web-dev-mcp/claude-md.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 | $0.00510 | $0.00510 |
| Opus 5 | $0.00255 | $0.00255 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
web-dev-mcp 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Stack Web Dev Toolkit MCP Server
Overview
- Server name:
fullstack_webdev - Entry point:
fullstack_webdev_server.py - Purpose: Serve curated documentation, quickstart commands, and deployment checklists for modern full stack web development tools.
Available Tools
list_tool_categories– Enumerate catalog categories and their tool members.fetch_tool_reference– Fetch summary, docs link, install commands, and optional HTTP status for a specific tool.framework_quickstart– Generate starter commands for Next.js, SvelteKit, Remix, or Nuxt across npm, pnpm, yarn, and bun.recommend_stack– Propose a stack based on project description, experience level, and realtime needs.deployment_checklist– Output opinionated deployment steps and notes for Vercel, Netlify, or Cloudflare Pages.
Configuration
- Optional environment variable:
FULLSTACK_WEBDEV_DEFAULT_PROVIDER(defaults tovercel). - No API keys or secrets are required; any secrets block in catalogs can be omitted.
Operational Notes
- All logging is routed to stderr via Python
logging. - HTTP status checks use
httpx.AsyncClient().head()with a 5-second timeout. - Outputs use emoji markers for clarity while remaining plaintext-friendly.
Testing
Install dependencies first (e.g., python3 -m venv .venv && source .venv/bin/activate && pip install -r requirements.txt).
python fullstack_webdev_server.py
printf '%s\n' \
'{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"local-test","version":"0.0.1"}}}' \
'{"jsonrpc":"2.0","method":"notifications/initialized","params":{}}' \
'{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
| python fullstack_webdev_server.py
Extending
- Append new tool metadata in
RAW_TOOL_DATA. - Add quickstart metadata in
FRAMEWORK_STARTERSor deployment details inDEPLOYMENT_PLAYBOOKS. - Construct new MCP tools by following the existing pattern: sanitize input via
.strip(), log intent, handle errors, and return formatted strings only.
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 · 39 lines · 510 tokens per session scan A aeda9f557f9b
web-dev-mcp CLAUDE.md is an instructions file published in the GitHub repository razdo227/web-dev-mcp (0 stars, last pushed 10mo ago), licensed MIT. It adds 510 tokens to every session, about $0.0026 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
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).
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.
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.