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/lozit/mcp-standardnotes/claude-mdgit clone --depth 1 https://github.com/lozit/mcp-standardnotesWrote 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/lozit/mcp-standardnotes/claude-md)<a href="https://agentmods.dev/instructions/lozit/mcp-standardnotes/claude-md"><img src="https://agentmods.dev/badge/instructions/lozit/mcp-standardnotes/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.01487 | $0.01487 |
| Opus 5 | $0.00744 | $0.00744 |
| Sonnet 5 | $0.00297 | $0.00297 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
mcp-standardnotes 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Standard Notes
MCP (Model Context Protocol) server that lets Claude interact with a Standard Notes account (read, create, edit, delete notes and tags) while preserving Standard Notes' end-to-end encryption (E2EE).
What is implemented locally = only the Standard Notes protocol 004 framing (payload format 004:<nonce>:<ciphertext>:<aad>, root key derivation → masterKey/serverPassword, items_key wrap/unwrap). That's parsing/serialization of a documented public format, not new cryptography.
The @standardnotes/snjs package and the modular @standardnotes/{encryption,models,...} packages were ruled out: the monolith is deprecated (Node 16 only), and the modular packages have un-propagated breaking changes (ContentType removed from common) that make them unusable externally.
Stack
- Language: TypeScript (strict)
- Runtime: Node.js ≥ 20
- MCP SDK:
@modelcontextprotocol/sdk - Crypto:
libsodium-wrappers-sumo(Argon2id + XChaCha20-Poly1305 IETF) - HTTP: native
fetch(Node 20+) - MCP transport: stdio (local, no network exposure)
Commands
npm install # Install dependencies
npm run build # Compile TypeScript → dist/
npm run dev # Watch mode (tsx)
npm run typecheck # Type-check without emitting
npm test # Run tests (vitest)
npm run lint # ESLint
Structure
src/
index.ts # MCP stdio entry point
server.ts # McpServer + tool registration
cli/login.ts # `npm run login` — interactive prompt + keychain
sn/
client.ts # Orchestration: login/session → HTTP + protocol
crypto.ts # libsodium wrapper (argon2id, xchacha20poly1305)
protocol004.ts # SN 004 framing: root key, items_key wrap, payload enc/dec
http.ts # fetch wrapper: /v1/login-params, /v1/login, /v1/items/sync
session.ts # Session persistence via keytar
types.ts # Note / NoteSummary / KeyParams types
tools/notes.ts # MCP handlers + zod schemas
tools/tags.ts # Tags + sync handlers + zod schemas
security/
redact.ts, logger.ts
.env.example
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 · 111 lines · 1,487 tokens per session scan A 5ed489096f03
mcp-standardnotes CLAUDE.md is an instructions file published in the GitHub repository lozit/mcp-standardnotes (9 stars, last pushed 3d ago), licensed MIT. It adds 1,487 tokens to every session, about $0.0074 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
linkedin-mcp-server AGENTS.md
AGENTS.md instructions for stickerdaniel/linkedin-mcp-server, covering claude.md, development commands, scraping rules, browser identity rules and profile safety rules.
pagespeed-insights-mcp AGENTS.md
AGENTS.md instructions for ruslanlap/pagespeed-insights-mcp, covering project rules — pagespeed-insights-mcp (mcp server), специфіка проєкту, обов'язкові практики (mcp + ts), serena + .serena/ and професійні skills тільки.
kafka-schema-reg-mcp AGENTS.md
AGENTS.md instructions for aywengo/kafka-schema-reg-mcp, covering development guidelines, prerequisites, quick setup, install dependencies and install dev dependencies (optional but recommended).
ls-mcp AGENTS.md
AGENTS.md instructions for lirantal/ls-mcp, covering agents.md, start here, documentation, prs and issues and releases.
PBP CLAUDE.md
Instructions for MadGapun/PBP, covering pbp — claude-code-memory, stand 2026-08-25 (v1.7.23 stable) — ehrliche zahlen, stand 2026-07-16 (v1.8.0-beta.6, prerelease) — hotfix #760, stand 2026-07-14 (v1.7.7) — scoring-fairness & praxis-funde and stand 2026-07-03 (v1.7.6) — alltags-fuehrung.
Instability CLAUDE.md
Instructions for tcpiplab/Instability, covering claude.md, commands, code style guidelines & design philosophy, v3 project architecture and core components (v3).