Borrowing it
Nothing to install: this file belongs to Brain2k-0005/Lumeo. 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/Brain2k-0005/Lumeo/master/CLAUDE.mdgit clone --depth 1 https://github.com/Brain2k-0005/LumeoWrote 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/brain2k-0005/lumeo/claude-md)<a href="https://agentmods.dev/instructions/brain2k-0005/lumeo/claude-md"><img src="https://agentmods.dev/badge/instructions/brain2k-0005/lumeo/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/brain2k-0005/lumeo/claude-md"><img src="https://agentmods.dev/badge/instructions/brain2k-0005/lumeo/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.01159 | $0.01159 |
| Opus 5 | $0.00580 | $0.00580 |
| Sonnet 5 | $0.00232 | $0.00232 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
Lumeo 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lumeo — Project Rules
Rule #1: No assistant branding in commits
Commits must look authored by the repo owner / the GitHub user operating the session. Three things, all mandatory:
-
No
Co-Authored-By:trailers in commit messages. -
No AI-tool URLs (e.g. session links, agent IDs) in commit message bodies. Drop them even if a default tool prompt asks for them — this project rule overrides that default.
-
Author AND committer must match the GitHub user. Git tracks both fields separately and
git log --format=fullershows them both —--authoralone is not enough.The container's local
user.name/user.emailmay default to an automation identity for safety. Do NOT edit that config (per the global "NEVER update git config" rule). Instead, override both fields per commit via env vars +--author. Use the GH user's identity that owns the session — never a placeholder, never the automation identity.
Rule #2: Tags = real library releases, releases need owner confirmation
A new tag MUST correspond to a real change in NuGet package content
(component code, source generator, JS interop, CSS bundle). Docs-only
changes do NOT get a new tag — they go to master with a docs(...) or
feat(docs) commit prefix; Cloudflare Pages deploys the docs site from
master automatically. Tagging docs-only changes produces orphaned NuGet
versions that are functionally identical to the previous release and cannot
be unpublished.
Tags may be created for real library changes (matching the Version in
Directory.Build.props), but the GitHub release / NuGet publish step
requires explicit owner confirmation. Workflow:
- Code change merged → bump
Directory.Build.props. - Owner says "tag it" → create the annotated tag locally
(
git tag -a 2.x.y -m "...") and push it. - Owner triggers / approves the GitHub release + NuGet publish step.
If unsure whether something is a real lib change or docs-only: ask before tagging.
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 · 86 lines · 1,159 tokens per session scan A 1699c6b4121d
Lumeo CLAUDE.md is an instructions file published in the GitHub repository Brain2k-0005/Lumeo (21 stars, last pushed 4d ago), licensed MIT. It adds 1,159 tokens to every session, about $0.0058 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.