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/mirkosertic/mcpluceneserver/claude-mdgit clone --depth 1 https://github.com/mirkosertic/MCPLuceneServerWrote 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/mirkosertic/mcpluceneserver/claude-md)<a href="https://agentmods.dev/instructions/mirkosertic/mcpluceneserver/claude-md"><img src="https://agentmods.dev/badge/instructions/mirkosertic/mcpluceneserver/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.00876 | $0.00876 |
| Opus 5 | $0.00438 | $0.00438 |
| Sonnet 5 | $0.00175 | $0.00175 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
MCPLuceneServer 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Lucene Server - AI Assistant Guide
For user-facing documentation, see README.md.
Critical Rules
- ALWAYS use the
implement-review-loopagent for code changes - ALWAYS update README.md when adding, removing, or changing:
- MCP tools (add tool documentation)
- Configuration options
- User-facing behavior
- Troubleshooting information
- NEVER duplicate README content here - this file is for development context only
- Test with real documents before considering a feature complete
- Always use Context7 MCP when I need library/API documentation, code generation, setup or configuration steps without me having to explicitly ask.
- ALWAYS bump
SCHEMA_VERSIONinDocumentIndexer.javawhen changing the index schema (adding/removing/renaming fields, changing analyzers, or modifying field indexing options)
Key Components
| Component | File | Responsibility |
|---|---|---|
| SearchTools | tools/SearchTools.java |
simpleSearch, extendedSearch, semanticSearch, profileQuery, profileSemanticSearch, suggestTerms, getTopTerms |
| CrawlerTools | tools/CrawlerTools.java |
startCrawl, getCrawlerStats/Status, pause/resume, directory management |
| IndexInfoTools | tools/IndexInfoTools.java |
getIndexStats, listIndexedFields, getDocumentDetails |
| IndexAdminTools | tools/IndexAdminTools.java |
indexAdmin, optimizeIndex, purgeIndex, unlockIndex, getIndexAdminStatus, UiResource |
| LuceneIndexService | index/LuceneIndexService.java |
Lucene IndexWriter/Searcher, NRT, admin ops, semantic search |
| DocumentCrawlerService | crawler/DocumentCrawlerService.java |
Directory walking, batch processing, state management |
| FileContentExtractor | crawler/FileContentExtractor.java |
Apache Tika integration, metadata extraction |
| DocumentIndexer | crawler/DocumentIndexer.java |
Lucene document creation, field schema |
| CrawlerConfigurationManager | crawler/CrawlerConfigurationManager.java |
Config file persistence (~/.mcplucene/config.yaml) |
| DirectoryWatcherService | crawler/DirectoryWatcherService.java |
File system monitoring for real-time updates |
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.
- 5d ago First seen · 77 lines · 876 tokens per session scan A 09e2207f1e47
MCPLuceneServer CLAUDE.md is an instructions file published in the GitHub repository mirkosertic/MCPLuceneServer (5 stars, last pushed today), licensed Apache-2.0. It adds 876 tokens to every session, about $0.0044 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
mcp-server-excel readme-management.instructions.md
Instructions for sbroenne/mcp-server-excel, covering readme management - quick reference, core entry documents, feature documentation, critical rules and tool & action counts must match.
mcp-server-excel extension-development.instructions.md
Instructions for sbroenne/mcp-server-excel, covering vs code extension development instructions, extension overview, changelog and changesets (critical), version management and automatic version management (unified release workflow).
init-knowledge-base AGENTS.md
Instructions for lululu811/init-knowledge-base, covering agents.md — init-knowledge-base, 项目概述, 技术栈与运行时架构, 运行时架构 and 目录结构与模块划分.
deckforge CLAUDE.md
Instructions for Whatsonyourmind/deckforge, covering deckforge, tech stack, project structure, key commands and local development.
ocr-mcp copilot-instructions.md
Copilot instructions for sandraschi/ocr-mcp: You have access to a FastMCP 3.4+ OCR server with 14 backends for document text extraction.
oorep-mcp AGENTS.md
AGENTS.md instructions for Dhi13man/oorep-mcp, covering agent operating manual — oorep mcp, mission & scope, core workflow, technical guardrails and coding style & tooling.