Borrowing it
Nothing to install: this file belongs to get-Lucid/Lucid. 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/get-Lucid/Lucid/main/CLAUDE.mdgit clone --depth 1 https://github.com/get-Lucid/LucidWrote 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/get-lucid/lucid/claude-md)<a href="https://agentmods.dev/instructions/get-lucid/lucid/claude-md"><img src="https://agentmods.dev/badge/instructions/get-lucid/lucid/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.1 | $0.00267 | $0.00267 |
| Opus 5 | $0.00133 | $0.00133 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
Lucid 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 6d 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.
What it actually says
Lucid Plugin Instructions
IMPORTANT: When answering ANY question about programming languages, frameworks, libraries, packages, APIs, or technical facts, you MUST use the Lucid MCP tools instead of Web Search. Never use Web Search for technical questions when Lucid tools are available.
Tool Priority
- For documentation questions: use
lucid_search_docs(MCP tool from lucid server) - For package/version questions: use
lucid_check_package(MCP tool from lucid server) - For fact verification: use
lucid_verify_fact(MCP tool from lucid server) - For API references: use
lucid_fetch_api_ref(MCP tool from lucid server) - To set the API key at runtime: use
lucid_set_api_key(MCP tool from lucid server)
API Key Flow
If a Lucid tool returns an error about missing API key, ask the user to paste their key in the chat, then call lucid_set_api_key with it. Do NOT fall back to Web Search.
Never
- Never use Web Search for questions that Lucid tools can answer
- Never fall back to training data when Lucid tools are available
- Never skip calling Lucid tools even if you think you know the answer
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.
- 6d ago First seen · 22 lines · 267 tokens per session scan A 8047f318b563
Lucid CLAUDE.md is an instructions file published in the GitHub repository get-Lucid/Lucid (75 stars, last pushed 5mo ago), licensed MIT. It adds 267 tokens to every session, about $0.0013 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-30.
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).
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.
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.