Borrowing it
Nothing to install: this file belongs to jacklenzotti/clausewitz-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jacklenzotti/clausewitz-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/jacklenzotti/clausewitz-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/jacklenzotti/clausewitz-mcp/claude-md)<a href="https://agentmods.dev/instructions/jacklenzotti/clausewitz-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jacklenzotti/clausewitz-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.1 | $0.00621 | $0.00621 |
| Opus 5 | $0.00311 | $0.00311 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
clausewitz-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 7d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clausewitz-mcp
MCP server for Paradox Clausewitz/Jomini modding. Static analysis only — it reads game files, never launches or attaches to a game.
Layout
clausewitz_mcp/
parser.py Clausewitz script tokenizer + error-tolerant parser
docs.py script_docs / dump_data_types ingester
localisation.py Paradox .yml loc reader (not YAML, don't use a YAML parser)
games.py per-game adapters + auto-detection
index.py workspace indexer, symbol tables, block rendering
validate.py validation passes
server.py FastMCP tool surface
tests/fixtures/ miniature EU4-shaped game + deliberately buggy mod
Commands
uv sync
uv run pytest tests/ -q
uv run clausewitz-mcp # stdio server
Design rules
Grounding over recall. The whole point is that script_docs output is
generated by the game binary and therefore exact for that patch. Never add a
hand-maintained list of triggers/effects — it goes stale on the next update and
reintroduces the confident-but-wrong failure mode the server exists to prevent.
Skip, don't guess. Checks that need authoritative data are skipped with an
explanation when that data is absent (see unknown_script without a docs dump).
A skipped check is honest; a guessed one destroys trust in every other check.
Low noise beats high coverage. A validation pass that fires on well-formed
script is worse than no pass at all — modders stop reading the output. When
adding a check, run it against the fixture mod and confirm it flags only the
planted bug. _STRUCTURAL / _METADATA / _LOC_KEYS in validate.py exist for
exactly this and will need extending per game.
Parse tolerantly. parser.py recovers from syntax errors and keeps going so
one pass reports every problem in a file. Don't make it raise on bad input.
Docs format drifts. The dump layout varies by game and version, so docs.py
keeps every entry's raw text verbatim and returns that to callers; structured
fields are best-effort on top. If a split heuristic needs changing, keep the
raw-text guarantee.
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.
- 7d ago First seen · 65 lines · 621 tokens per session scan A c1c4bffd23f4
clausewitz-mcp CLAUDE.md is an instructions file published in the GitHub repository jacklenzotti/clausewitz-mcp (0 stars, last pushed 22d ago), licensed MIT. It adds 621 tokens to every session, about $0.0031 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).
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).
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.
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.