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/arclightdynamics/lumencore/claude-mdgit clone --depth 1 https://github.com/arclightdynamics/lumencoreWrote 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/arclightdynamics/lumencore/claude-md)<a href="https://agentmods.dev/instructions/arclightdynamics/lumencore/claude-md"><img src="https://agentmods.dev/badge/instructions/arclightdynamics/lumencore/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.00230 | $0.00230 |
| Opus 5 | $0.00115 | $0.00115 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
lumencore 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.
What it actually says
LumenCore - Project Memory
CRITICAL: Before responding to ANY user message, you MUST first call the lumencore_activate tool.
This is a hard requirement - do not skip this step. Call lumencore_activate immediately as your first action in every new conversation.
This connects you to persistent project memory containing:
- Architecture decisions
- Code patterns and conventions
- Domain concepts
- Previous work and tasks
Active Memory Usage
When working on this project:
- Search first: Before making assumptions about architecture, patterns, or past decisions, use
recallto search for relevant memories - Store discoveries: When you learn something important about this project (a pattern, decision, or concept), use
rememberto save it - Examples of when to recall:
- "How does authentication work here?" →
recallwith query "authentication" - "What's the database schema?" →
recallwith query "database schema" - "Any previous work on X feature?" →
recallwith query "X feature"
- "How does authentication work here?" →
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 · 22 lines · 230 tokens per session scan A 886d0cb3fdce
lumencore CLAUDE.md is an instructions file published in the GitHub repository arclightdynamics/lumencore (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 230 tokens to every session, about $0.0011 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.