Borrowing it
Nothing to install: this file belongs to psenger/obsidian-markdown-lint-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.
curl -O https://raw.githubusercontent.com/psenger/obsidian-markdown-lint-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/psenger/obsidian-markdown-lint-mcp-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/psenger/obsidian-markdown-lint-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/psenger/obsidian-markdown-lint-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/psenger/obsidian-markdown-lint-mcp-server/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/psenger/obsidian-markdown-lint-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/psenger/obsidian-markdown-lint-mcp-server/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.02051 | $0.02051 |
| Opus 5 | $0.01026 | $0.01026 |
| Sonnet 5 | $0.00410 | $0.00410 |
| Haiku 4.5 | $0.00205 | $0.00205 |
Grade A, and why
obsidian-markdown-lint-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 9d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
obsidian-markdown-lint-mcp-server
Project overview
TypeScript stdio MCP server that lints markdown, validates front matter, and renders Mermaid diagrams to SVG. Claude Code launches it as a subprocess (docker run -i --rm) and talks JSON-RPC over stdin/stdout — no port, no long-running container. All tools are content-in/content-out — no volume mounts, no disk access. Claude Code owns all file I/O.
Build and run
npm run build # compile TypeScript → dist/
npm test # Jest unit tests (52 tests, >90% coverage)
npm run test:coverage # tests + coverage report
docker build -t obsidian-markdown-lint-mcp . # build the stdio server image (or: docker compose build)
Running evals
Trigger phrase: When asked to "run evals", "evaluate the tools", "check tool quality", or "test tool correctness":
- Run:
npm run eval - Parse the JSON output from stdout
- Report the summary and any failing evals
- If any fail, investigate the failing tool function
The eval runner calls the compiled tool functions directly (no Docker required). Results are JSON with summary.passed, summary.failed, and a results array with per-eval details.
Example invocation:
npm run eval 2>&1 | head -50
Snapshot harness
npm run snapshot proves that each un-embedded input reproduces its committed output through the real tool pipeline (test-1 launches Puppeteer, unlike the evals which mock rendering). Every fixture is an original/ (input) + snap-shot/ (expected output) pair under test-obsidian-vault/, with .markdownlint.json and .schemas/ at the vault root shared by all:
- test-1 —
render_mermaid_diagrams:original/test-1.mdhas```mermaidfences and nomermaid_svg_source;snap-shot/test-1.md+attachments/snap-shot/test-1/*.svgare the rendered result. - test-2 —
lint_markdown(no SVG):original/test-2.mdhas auto-fixable lint issues (MD004/009/010/012/034/049/050);snap-shot/test-2.mdis the tool'sfixed_contentand lints clean. - test-3 —
validate_front_matter(no SVG):original/test-3.mdhas front matter that fails the article schema (missingauthor, badcategory/statusenums, too fewtags);snap-shot/test-3.mdis the corrected, valid version.
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.
- 9d ago First seen · 133 lines · 2,051 tokens per session scan A 88a8a4216ff2
obsidian-markdown-lint-mcp-server CLAUDE.md is an instructions file published in the GitHub repository psenger/obsidian-markdown-lint-mcp-server (2 stars, last pushed yesterday), licensed MIT. It adds 2,051 tokens to every session, about $0.0103 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.