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/sirrlock/mcp/claude-mdgit clone --depth 1 https://github.com/sirrlock/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/sirrlock/mcp/claude-md)<a href="https://agentmods.dev/instructions/sirrlock/mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/sirrlock/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 | $0.00833 | $0.00833 |
| Opus 5 | $0.00417 | $0.00417 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
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 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@sirrlock/mcp — Claude Development Guide
Purpose
MCP (Model Context Protocol) server for Sirr — gives AI assistants direct access to
the Sirr secret vault. Published to npm as @sirrlock/mcp.
Stack
- TypeScript, Node 18+
@modelcontextprotocol/sdkfor MCP protocol- Native
fetch— no axios, no node-fetch @biomejs/biomefor lint + format- Jest + ts-jest for tests
Structure
src/
├── index.ts # MCP server entry: 5 tools, env vars (SIRR_SERVER, SIRR_TOKEN, SIRR_ORG)
└── helpers.ts # Pure helpers: parseKeyRef, path builders, formatTtl
Tools exposed (5 total)
| Tool | Description |
|---|---|
store_secret |
With name: org-scoped named secret (requires SIRR_ORG). Without: anonymous dead drop. |
read_secret |
By id: public dead drop. By name: org-scoped (requires SIRR_ORG). |
check_secret |
Metadata check without consuming a read. |
share_secret |
Burn-after-read link via sirrlock.com. No auth needed. |
audit |
Query the audit log. |
Everything else (webhooks, keys, orgs, roles, principals) is CLI/web-only — not exposed via MCP.
Routing semantics
store_secretwithoutname→POST /secrets(public dead drop). Returns{id}.store_secretwithname→POST /orgs/{SIRR_ORG}/secrets(org-scoped). Returns{key, id}. 409 if name exists.read_secretwithid→GET /secrets/{id}(public).read_secretwithname→GET /orgs/{SIRR_ORG}/secrets/{name}(org-scoped).share_secret→POST {SIRRLOCK_URL}/api/public/secret(sirrlock.com hosted).
Key Rules
- Never log or echo secret values in tool output
SIRR_ORGenv var is required for named secrets (store/read by name) and auditSIRR_TOKEN= master key for full access, or a principal key for org-scoped accesscheck_secretdoes NOT consume a read — safe to call freely- Tool descriptions tell Claude not to memorize or repeat retrieved secret values
store_secretwith a name returns 409 Conflict if the name already exists
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 · 84 lines · 833 tokens per session scan A 4d5721c2b964
mcp CLAUDE.md is an instructions file published in the GitHub repository sirrlock/mcp (0 stars, last pushed 14d ago), licensed MIT. It adds 833 tokens to every session, about $0.0042 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-09-01.
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).
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.
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).