Borrowing it
Nothing to install: this file belongs to Nano-Nimbus/locus. 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/Nano-Nimbus/locus/main/CLAUDE.mdgit clone --depth 1 https://github.com/Nano-Nimbus/locusWrote 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/nano-nimbus/locus/claude-md)<a href="https://agentmods.dev/instructions/nano-nimbus/locus/claude-md"><img src="https://agentmods.dev/badge/instructions/nano-nimbus/locus/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.00947 | $0.00947 |
| Opus 5 | $0.00474 | $0.00474 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
locus 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 7d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Purpose
Locus is a hierarchical markdown-based memory system for AI agents — each directory is a "room" (locus) in the palace, containing specific knowledge navigated on demand. Keeps context windows small while enabling precise, deep recall. Named for the atomic unit of the Method of Loci.
Must be agent-agnostic: usable by Claude, Codex, Gemini, or any LLM-based agent.
Existing Memory Patterns to Study
Before writing anything new, read these reference implementations:
| Location | What it shows |
|---|---|
~/.claude/projects/<project>/memory/ |
8-file memory system: MEMORY.md + specialty files |
~/.claude/projects/<project>/memory/ |
Multi-agent orchestration memory |
~/.claude/skills/*/SKILL.md |
Skill definition format (9 skills to study) |
~/.claude/commands/ |
Command format for reusable workflows |
A mature memory directory typically has a ~200-line MEMORY.md plus specialty files for gotchas, deployments, and platform services.
Memory File Conventions (from existing projects)
Structure of MEMORY.md:
- Project overview (1–3 sentences + key stats)
- Architecture/topology
- Configuration sections by subsystem
- Key file paths
- Current phase/status
- References to specialty files
Specialty file patterns:
technical-gotchas.md— header-per-issue, symptom → root cause → resolutionplatform-services.md— quick-reference table (service → version → IP/config)deployment-issues.md— numbered issues with detailed logging
Context window discipline: MEMORY.md is always loaded (~200 line limit enforced by auto-memory system). Specialty files are read on demand. This is the core design constraint the skill must encode.
Runtime Architecture
Locus has two complementary interfaces:
1. SKILL.md files — the primary interface. Skills live in ~/.claude/skills/<name>/SKILL.md
and are compatible with both Claude Code CLI and the Claude Agent SDK
(settingSources: ["user", "project"]). The existing 9 skills are references:
guided-walkthrough, project-triage, knowledge-capture, etc.
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.
- 7d ago First seen · 92 lines · 947 tokens per session scan A 81f5817c305b
locus CLAUDE.md is an instructions file published in the GitHub repository Nano-Nimbus/locus (0 stars, last pushed 5mo ago), licensed MIT. It adds 947 tokens to every session, about $0.0047 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
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).
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.
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).
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.