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/chrisp671/zenithbridge/claude-mdgit clone --depth 1 https://github.com/Chrisp671/ZenithBridgeWrote 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/chrisp671/zenithbridge/claude-md)<a href="https://agentmods.dev/instructions/chrisp671/zenithbridge/claude-md"><img src="https://agentmods.dev/badge/instructions/chrisp671/zenithbridge/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.01591 | $0.01591 |
| Opus 5 | $0.00796 | $0.00796 |
| Sonnet 5 | $0.00318 | $0.00318 |
| Haiku 4.5 | $0.00159 | $0.00159 |
Grade A, and why
ZenithBridge 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 4d 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.
This is a copy
98% identical to obsidian-claude-code-mcp CLAUDE.md — 7 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is an Obsidian plugin that implements MCP (Model Context Protocol) servers to enable Claude Code and Claude Desktop integration with Obsidian vaults. The plugin provides both WebSocket (for Claude Code CLI) and HTTP/SSE (for Claude Desktop) transports for maximum compatibility.
Development Commands
bun install- Install dependenciesbun run dev- Start compilation in watch modebun run build- Type check and build for productionbun run version patch|minor|major- Bump version and update manifest fileseslint main.ts- Run linting
Architecture
Core Components
- main.ts - Plugin entry point that orchestrates initialization, settings management, and server lifecycle
- src/settings.ts - Comprehensive settings management with real-time server status display
- src/mcp/ - MCP protocol implementation
- dual-server.ts - Manages both WebSocket and HTTP servers with tool registry
- server.ts - WebSocket server for Claude Code CLI integration
- http-server.ts - HTTP/SSE server for Claude Desktop (uses MCP spec 2024-11-05)
- handlers.ts - Request routing with separation of IDE/MCP concerns
- types.ts - TypeScript interfaces for MCP protocol
- src/ide/ - Claude Code IDE-specific functionality
- ide-handler.ts - Handles IDE-specific requests (ide_connected, etc.)
- ide-tools.ts - IDE-specific tool implementations (openDiff, close_tab, etc.)
- src/shared/ - Common functionality
- tool-registry.ts - Automatic tool registration and validation system
- src/obsidian/ - Obsidian API integration
- workspace-manager.ts - Tracks active file and selection using DOM events
- utils.ts - Path normalization and validation utilities
- src/tools/ - MCP tool implementations
- file-tools.ts - File read/write operations
- general-tools.ts - General workspace and file manipulation tools
- src/terminal/ - Optional embedded terminal feature
- terminal-view.ts - Terminal UI implementation using xterm.js
- pseudoterminal.ts - Platform-specific terminal spawning
- python-detection.ts - Python environment detection
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.
- 4d ago First seen · 155 lines · 1,591 tokens per session scan A 2692d7bc4ece
ZenithBridge CLAUDE.md is an instructions file published in the GitHub repository Chrisp671/ZenithBridge (1 stars, last pushed 2mo ago), licensed MIT. It adds 1,591 tokens to every session, about $0.0080 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to obsidian-claude-code-mcp CLAUDE.md, differing in 7 lines, and is treated as a copy.
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.