Borrowing it
Nothing to install: this file belongs to ZenixSolutions/lumics-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ZenixSolutions/lumics-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ZenixSolutions/lumics-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/zenixsolutions/lumics-mcp/claude-md)<a href="https://agentmods.dev/instructions/zenixsolutions/lumics-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/zenixsolutions/lumics-mcp/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.
<a href="https://agentmods.dev/instructions/zenixsolutions/lumics-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/zenixsolutions/lumics-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.02691 | $0.02691 |
| Opus 5 | $0.01345 | $0.01345 |
| Sonnet 5 | $0.00538 | $0.00538 |
| Haiku 4.5 | $0.00269 | $0.00269 |
Grade A, and why
lumics-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 9d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — instructions for AI agents working in this repository
This file governs AI agents (Claude Code and equivalents) making changes to lumics-mcp. Read it
before writing code. Human contributors should read CONTRIBUTING.md, which says
the same things in a different register.
Governance
This project is governed by the Engineering OS framework. Engineering OS defines how the project is built — architecture, standards, testing, security, workflow, review, and decision making. This repository defines what is being built.
Consequences for you:
- Engineering OS is the source of truth for process and convention. Follow it.
- Do not invent new conventions. If Engineering OS or this repository already defines one, use it. If neither does, ask rather than deciding silently.
- Where a repository requirement appears to conflict with Engineering OS, ask for clarification. Do not resolve the conflict on your own initiative.
- Distinguish facts, assumptions, inferences, and preferences when you report. Say "I have not verified this" when you have not.
Approval before implementation
Do not begin meaningful implementation without explicit approval. Silence is not approval, and neither is an ambiguous instruction that could be read as approval. This is Article V of the Engineering OS Constitution and it is the rule most likely to be broken by an eager agent.
The sequence is: issue → discovery → RFC where required → explicit owner approval → ADR → implementation → independent review → validation → merge approval.
Stop and ask for approval before:
- Meaningful implementation of any kind
- Architecture or layer-boundary changes
- Security-model changes, including anything touching credentials, redaction, or the gating flags
- Adding or upgrading a material dependency (see docs/DEPENDENCY_POLICY.md)
- Public interface changes — adding, removing, or renaming a tool, or changing its arguments
- Releases and meaningful merges
- Any deviation from an already-approved design
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.
- 9d ago First seen · 196 lines · 2,691 tokens per session scan A a8a9d2f1c728
lumics-mcp CLAUDE.md is an instructions file published in the GitHub repository ZenixSolutions/lumics-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 2,691 tokens to every session, about $0.0135 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.
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).
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.