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/williamzujkowski/mcp-standards-server/claude-mdgit clone --depth 1 https://github.com/williamzujkowski/mcp-standards-serverWrote 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/williamzujkowski/mcp-standards-server/claude-md)<a href="https://agentmods.dev/instructions/williamzujkowski/mcp-standards-server/claude-md"><img src="https://agentmods.dev/badge/instructions/williamzujkowski/mcp-standards-server/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.02985 | $0.02985 |
| Opus 5 | $0.01492 | $0.01492 |
| Sonnet 5 | $0.00597 | $0.00597 |
| Haiku 4.5 | $0.00298 | $0.00298 |
Grade A, and why
mcp-standards-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 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.
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Standards Server - LLM Context Management System
Last Updated: 2025-07-16
Status: ✅ FULLY OPERATIONAL SYSTEM - Complete standards ecosystem with verified Web UI and passing workflows
Project Overview
This project transforms the williamzujkowski/standards repository into a comprehensive LLM context management system by implementing a Model Context Protocol (MCP) server. The server provides intelligent, context-aware access to development standards, enabling LLMs to automatically select and apply appropriate standards based on project requirements.
Key Objectives
- MCP Server Implementation: Build a robust MCP server that exposes the standards repository as accessible tools for LLMs
- Intelligent Standard Selection: Implement rule-based and semantic search capabilities for automatic standard selection
- Token Optimization: Create efficient, LLM-friendly formats for standards consumption
- Compliance Integration: Support NIST 800-53r5 control mapping and compliance validation
- Hierarchical Organization: Structure standards with clear metadata and relationships
Comprehensive Standards Coverage
The system now includes 25 comprehensive standards covering the entire software development lifecycle:
🚀 Specialty Domain Standards (8)
- AI/ML Operations (MLOps) - Model lifecycle, ethical AI, monitoring
- Blockchain/Web3 Development - Smart contracts, DeFi, security
- IoT/Edge Computing - Device management, protocols, optimization
- Gaming Development - Engine architecture, performance, multiplayer
- AR/VR Development - Immersive experiences, spatial computing
- Advanced API Design - REST, GraphQL, gRPC patterns
- Database Design & Optimization - Schema design, performance tuning
- Sustainability & Green Computing - Carbon footprint, efficiency
🔧 Testing & Quality Standards (3)
- Advanced Testing Methodologies - Performance, security, chaos engineering
- Code Review Best Practices - Review workflows, automated checks
- Performance Tuning & Optimization - Profiling, caching, scaling
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 · 307 lines · 2,985 tokens per session scan A a9e0af67a463
mcp-standards-server CLAUDE.md is an instructions file published in the GitHub repository williamzujkowski/mcp-standards-server (3 stars, last pushed 5d ago), licensed MIT. It adds 2,985 tokens to every session, about $0.0149 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
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.
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).
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.
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).