What is seekstone CLAUDE.md?

Repository instructions for working on Seekstone, an Obsidian integration that provides direct access to files in an Obsidian vault, plus its measurement tools.

Use them when developing the server, shared packages or profiling and testing harness, especially for type-checking, tests and performance measurements.

They explain the project’s purpose, commands, architecture and benchmark harness so changes can be made and checked consistently.

How shaqmughal/seekstone configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to shaqmughal/seekstone. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/shaqmughal/seekstone/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/shaqmughal/seekstone

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/shaqmughal/seekstone/claude-md/github.svg)](https://agentmods.dev/instructions/shaqmughal/seekstone/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/shaqmughal/seekstone/claude-md"><img src="https://agentmods.dev/badge/instructions/shaqmughal/seekstone/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/shaqmughal/seekstone/claude-md"><img src="https://agentmods.dev/badge/instructions/shaqmughal/seekstone/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 902 This file is loaded in full into every session.

When invoked 902 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00902	$0.00902
Opus 5.5	$0.00361	$0.00361
Sonnet 5.5	$0.00180	$0.00180
Haiku 4.5	$0.00090	$0.00090

Measured 10d ago against content hash 1cb00e3b215d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

seekstone 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 10d 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.

CLAUDE.md · 30 lines

How it starts

The opening of the file, as written. The whole thing — 30 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.

What this repo is

seekstone is an Obsidian MCP server, published to npm as seekstone. The MCP server (packages/server) is the product: filesystem-direct vault access with low context-tax, shipped as a built single-file bundle. Alongside it lives the measurement harness (packages/harness) — a profiler + benchmark + write-safety suite that produced the payload numbers the server is designed around. The harness shares packages/core primitives with the server and is dev-only (run from source, not published).

The product story behind the harness (kept in version control because it's how the project will be evaluated): filesystem-direct beats REST-proxy, and the win is mostly payload size ("context tax"), not raw CPU. The harness exists to produce reproducible numbers that demonstrate that.

Commands

Harness commands (profile, bench, scenarios, safety, retrieval, fixture generation) live in packages/harness/CLAUDE.md.

The server has a real build — npm run build -w seekstone bundles it (and packages/core) to dist/index.js via tsup for publishing. The harness has no build step; it runs via tsx. tsc is used for typecheck only. Tests are co-located as *.test.ts next to source.

The server reads its own env vars — see the README's Configuration table. Write behavior to know before editing tools: deletes are recoverable (.trash/), every write tool supports optional prevHash compare-and-swap (moves and deletes included since 0.14.0; every mutating result returns a contentHash), moves rewrite inbound links, every write is policy-gated + atomic, and every write tool journals pre-images via journalWrite (single-file) or ctx.journal.begin() (multi-file: compute all rewrites first, journal them under one seq, then write) BEFORE the first vault byte changes so undo_write can restore the whole operation; .seekstone/ is excluded from the walker like .trash/; and dispatch audits every write-tool call when SEEKSTONE_AUDIT_FILE is set — a new write tool must return an audit detail object from its dispatch case (paths/counts only, never content) or its calls are not recorded (see docs/ARCHITECTURE.md §2).

Read the full file on GitHub · 30 lines

Changes

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.

10d ago Changed · +2 lines · +156 tokens per session 1cb00e3b215d
24d ago Changed · -18 lines · -370 tokens per session a67d3d98a005
2mo ago First seen · 46 lines · 1,116 tokens per session scan A 01f18316ed8d

Subscribe to this mod's changes

seekstone CLAUDE.md is an instructions file published in the GitHub repository shaqmughal/seekstone (35 stars, last pushed yesterday), licensed MIT. It adds 902 tokens to every session, about $0.0036 per session on Opus 5.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-30.

Backend and APIs Databases LLM ai claude markdown mcp model-context-protocol

seekstone CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
seekstone CLAUDE.mdshaqmughal/seekstone	Instructions file	35	yesterday	MIT	A	902	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

seekstone: Instructions file for Claude Code