n2n-nexus: Instructions file for Claude Code

CLAUDE.md

n2n-nexus CLAUDE.md is an instructions file for Claude Code from n2ns/n2n-nexus. It costs 705 tokens per session, scanned A, original, Apache-2.0.

A project instruction file for n2n-nexus, documenting its commands, tests, local servers, and code structure.

In plain words
What is it for?
Running all tests or one test file, starting the daemon or MCP server locally, and understanding the TypeScript entry points and architecture.
Why use it?
It gives the coding agent the repository-specific details needed to build, test, lint, and run the project correctly.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is n2ns/n2n-nexus's own configuration. It tells Claude Code how to work on n2n-nexus itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything n2n-nexus configures →

Reuse

Borrowing it

Nothing to install: this file belongs to n2ns/n2n-nexus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/n2ns/n2n-nexus/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/n2ns/n2n-nexus

Made for: Claude Code.

Wrote 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.

agentmods badge for n2n-nexus CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/n2ns/n2n-nexus/claude-md.svg)](https://agentmods.dev/instructions/n2ns/n2n-nexus/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/n2ns/n2n-nexus/claude-md"><img src="https://agentmods.dev/badge/instructions/n2ns/n2n-nexus/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 705 This file is loaded in full into every session.
When invoked 705 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00705 $0.00705
Opus 5 $0.00352 $0.00352
Sonnet 5 $0.00141 $0.00141
Haiku 4.5 $0.00071 $0.00071

Measured 8d ago against content hash 9962601d5ece, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

n2n-nexus 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 8d 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.

CLAUDE.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 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.

Commands

npm run build          # tsc → build/
npm run dev            # tsc -w (watch mode)
npm test               # vitest run (all tests)
npm run lint           # eslint src/**

# Run a single test file
npx vitest run tests/daemon_messages.test.ts

# Run daemon locally
node build/index.js daemon --root /tmp/nexus-test --port 5688

# Run MCP server locally
NEXUS_ENDPOINT=http://127.0.0.1:5688 node build/index.js mcp

Pre-commit runs lint; pre-push runs build && test (via lefthook).

Architecture

The daemon + MCP refactor is complete (v0.5.0). See REFACTOR_PLAN.md for the full rationale.

Entry point

src/index.ts routes to runDaemon() (src/daemon/) or NexusServer().run() (src/server/nexus.ts) based on the first CLI argument (daemon or default).

Daemon (src/daemon/)

server.ts — plain http.Server with all REST endpoints. Contains TOOL_DEFINITIONS (20 tools with JSON Schema), per-instance session map (Map<instanceId, {currentProject}>), and individual tool handler functions. Routes: GET /api/tools, POST /api/tools/call, plus project/message/meeting/task/maintenance endpoints.

MCP Server (src/server/nexus.ts)

Pure stateless proxy. On startup: connects stdio transport, then tries GET /api/tools; if daemon unreachable, schedules 3-second retry loop. On connect: calls server.sendToolListChanged(). CallToolPOST /api/tools/call. No hardcoded tool names.

Storage layer (src/storage/) — unchanged

  • StorageManager (index.ts) is the single access point; delegates to sub-modules
  • sqlite.ts + sqlite-meeting.ts — SQLite with WAL mode for meetings, tasks, read cursors
  • store.ts (UnifiedMeetingStore) — auto-selects SQLite or JSON fallback for meetings
  • registry.ts / projects.ts / logs.ts / docs.ts — JSON file-based storage for projects, global docs, logs
  • paths.ts — all file paths derived from getRootPath() which reads NEXUS_ROOT env or ~/.n2n-nexus

Read the full file on GitHub · 61 lines

Changes

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.

  1. 8d ago First seen · 61 lines · 705 tokens per session scan A 9962601d5ece

Subscribe to this mod's changes

n2n-nexus CLAUDE.md is an instructions file published in the GitHub repository n2ns/n2n-nexus (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 705 tokens to every session, about $0.0035 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.

Related

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens