stellavault: Instructions file for Claude Code

CLAUDE.md

stellavault CLAUDE.md is an instructions file for Claude Code from Evanciel/stellavault. It costs 662 tokens per session, scanned A, original, MIT.

Project instructions for Stellavault, a self-compiling knowledge server built with Node.js and TypeScript in a monorepo, where related packages share one repository.

In plain words
What is it for?
Use them when developing Stellavault features, especially changes involving its knowledge workflow, federation security, or threat-model review.
Why use it?
They give an agent the project's architecture, commands, security rules, and required checks before it changes code.

Instructions file for Claude Code

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

This is Evanciel/stellavault's own configuration. It tells Claude Code how to work on stellavault 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 stellavault configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Evanciel/stellavault. 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/Evanciel/stellavault/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Evanciel/stellavault

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 stellavault CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/evanciel/stellavault/claude-md.svg)](https://agentmods.dev/instructions/evanciel/stellavault/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/evanciel/stellavault/claude-md"><img src="https://agentmods.dev/badge/instructions/evanciel/stellavault/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 662 This file is loaded in full into every session.
When invoked 662 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.00662 $0.00662
Opus 5 $0.00331 $0.00331
Sonnet 5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

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

Security

Grade A, and why

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

CLAUDE.md · 46 lines

What it actually says

Stellavault — Project Rules

Project Info

  • Name: Stellavault — Self-compiling knowledge MCP server
  • Version: 0.7.4
  • GitHub: https://github.com/Evanciel/stellavault
  • npm: stellavault (688KB published, 2.4MB unpacked)
  • Stack: Node.js 20+, TypeScript, ESM, Monorepo (npm workspaces)
  • Packages:
    • Bundled into root (same version): @stellavault/core (21 MCP tools), @stellavault/cli (39+ commands), @stellavault/graph (3D UI)
    • Independent versioning: @stellavault/sync (1.x — Notion↔Obsidian daemon), @stellavault/desktop (0.1.x — Electron app, separate GitHub release)
  • Architecture: Karpathy self-compiling KB (ingest→compile→wiki→session→flush loop)
  • Security baseline (v0.7.4): Codex SECURITY 8/10. Ed25519 federation + signed envelopes, header-only API token, CORS allow-list, federation experimental off-by-default (STELLAVAULT_FEDERATION_EXPERIMENTAL=1 to enable).

Autopilot 추가 규칙

Threat Model Gate (Phase 6 필수)

모든 기능 구현 후 Quality Gate에서 반드시 아래 질문을 검증할 것:

  1. 악의적 입력: 이 기능에 가짜/오염된 데이터를 넣으면 어떻게 되는가?
  2. 서비스 거부: 이 기능을 대량으로 호출하면 시스템이 멈추는가?
  3. 프라이버시 유출: 이 기능이 의도치 않게 개인 정보를 노출하는가?
  4. 신뢰 악용: 이 기능의 신뢰 메커니즘을 우회할 수 있는가?
  5. 데이터 무결성: 이 기능이 기존 데이터를 손상시킬 수 있는가?

위협 발견 시:

  • Critical → 구현 중단, 방어 로직 추가 후 재검증
  • Medium → Phase 7(Iterate)에서 방어 추가
  • Low → 이슈로 기록, 다음 사이클에서 처리

Federation 보안 원칙

  • 원문 텍스트는 절대 네트워크 전송 금지
  • 검색 결과: 제목 + 유사도 + 50자 스니펫만
  • blocked 노드(reputation=0)의 결과는 필터링
  • 새 노드는 neutral(40점)에서 시작, 자동 평판 적립

코드 컨벤션

  • Design reference: // Design Ref: §{section} — {rationale}
  • Success criteria: // Plan SC: {criteria being addressed}
  • Federation 메시지: JSON + newline delimiter
  • 에러 처리: StellavaultError with code + suggestion
  • i18n: 사용자 노출 문자열은 t() 함수 사용 권장
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. 7d ago First seen · 46 lines · 662 tokens per session scan A 1dc69022eea1

Subscribe to this mod's changes

stellavault CLAUDE.md is an instructions file published in the GitHub repository Evanciel/stellavault (4 stars, last pushed 13d ago), licensed MIT. It adds 662 tokens to every session, about $0.0033 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.

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