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/otolab/search-docs/claude-mdgit clone --depth 1 https://github.com/otolab/search-docsWrote 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/otolab/search-docs/claude-md)<a href="https://agentmods.dev/instructions/otolab/search-docs/claude-md"><img src="https://agentmods.dev/badge/instructions/otolab/search-docs/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.00005 | $0.00005 |
| Opus 5 | $0.00003 | $0.00003 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00001 | $0.00001 |
Grade A, and why
search-docs 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 3d 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
100% identical to deepseek-harness CLAUDE.md — 3 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.
What it actually says
@AGENTS.md
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.
- 3d ago First seen · 2 lines · 5 tokens per session scan A 336cc4fbf19b
search-docs CLAUDE.md is an instructions file published in the GitHub repository otolab/search-docs (1 stars, last pushed 3mo ago), licensed MIT. It adds 5 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to deepseek-harness CLAUDE.md, differing in 3 lines, and is treated as a copy.
Other instructions, from other repositories
PixelRAG CLAUDE.md
Instructions for StarTrail-org/PixelRAG, covering pixelrag, layout and conventions.
OpenDocuments AGENTS.md
Instructions for joungminsung/OpenDocuments, covering agents.md, project overview, monorepo structure, common commands and 특정 패키지만.
pdf-inline-image-rag-mcp AGENTS.md
AGENTS.md instructions for Joncallim/pdf-inline-image-rag-mcp, covering pdf inline image rag mcp agent guide, invariants, repository map, focused workflow and validation.
doctree-mcp CLAUDE.md
Claude Code instructions for joesaby/doctree-mcp, covering claude.md — doctree-mcp, project overview, architecture, key design decisions and data flow.
google-drive-rag-mcp AGENTS.md
AGENTS.md instructions for asamiile/google-drive-rag-mcp, covering google drive rag mcp — agent instructions, project overview, key files, running the server and install dependencies.
MCP-Google-Doc CLAUDE.md
Claude Code instructions for ophydami/MCP-Google-Doc, covering claude.md, build & run, architecture, current state and target architecture: vector rag support tool.