cosmos-os: Instructions file for Claude Code

CLAUDE.md

cosmos-os CLAUDE.md is an instructions file for Claude Code from ludeo-labs/cosmos-os. It costs 441 tokens per session, scanned A, original, MIT.

Project instructions for Cosmos, a web application whose scenarios and services are displayed on an interactive map. It documents commands, file layout, data flow, and rules that must remain true.

In plain words
What is it for?
It guides development, production builds, data validation, and the addition of services and scenarios.
Why use it?
It helps agents make changes without serving stale code or breaking links, identifiers, phases, or map behavior.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions Claude Code.

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

Reuse

Borrowing it

Nothing to install: this file belongs to ludeo-labs/cosmos-os. 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/ludeo-labs/cosmos-os/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/ludeo-labs/cosmos-os

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 cosmos-os CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ludeo-labs/cosmos-os/claude-md/github.svg)](https://agentmods.dev/instructions/ludeo-labs/cosmos-os/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/ludeo-labs/cosmos-os/claude-md"><img src="https://agentmods.dev/badge/instructions/ludeo-labs/cosmos-os/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.

agentmods 80×15 button for cosmos-os CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ludeo-labs/cosmos-os/claude-md"><img src="https://agentmods.dev/badge/instructions/ludeo-labs/cosmos-os/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 441 This file is loaded in full into every session.
When invoked 441 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.00441 $0.00441
Opus 5 $0.00220 $0.00220
Sonnet 5 $0.00088 $0.00088
Haiku 4.5 $0.00044 $0.00044

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

Security

Grade A, and why

cosmos-os 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.

CLAUDE.md · 28 lines

What it actually says

The Cosmos — notes for Claude Code

Commands

npm run dev        # dev server on :5173
npm run build      # tsc -b && vite build — the gate for every change
npm run validate   # data sanity: ids resolve, phaseIds unique, spacing ok

Never run tsc without --noEmit/-b — emitted .js files shadow .tsx in Vite and the app silently serves stale code.

Layout

  • src/scenarios/ — the entire universe as typed data: services.ts, topics.ts, scenarios.ts (domains + scenarios), owners.ts (teams), steps/<domain>.ts, barrel in data.ts. Most changes belong here.
  • src/map/ — SVG map rendering: Map.tsx (orchestration, layout edit mode), edge-resolver.ts (how a step becomes edges; special-cases the expandable realtime-hub), edge-builder.ts (bezier geometry).
  • src/components/ — UI shell: intro, playback controls, step panel, tech icons.
  • drift-sync/ — the nightly honesty pipeline (its own README).
  • .claude/skills/add-service and add-scenario: THE documented procedures for growing the map. Follow them rather than improvising.

Invariants

  • phaseId global, unique, never reused; every step's phase equals its scenario's phaseId.
  • Step from/to/via/through must exactly match SERVICES[].id / TOPICS[].id.
  • Service hex must match its color CSS token hue (src/styles/tokens.css); topics always TOPIC_COLOR/TOPIC_HEX.
  • World is 2400×1400; capsules ≥150px apart center-to-center.
  • Demo data is fictional (AstroMart). Keep it that way — no real company names/endpoints.
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. 9d ago First seen · 28 lines · 441 tokens per session scan A f13208f31778

Subscribe to this mod's changes

cosmos-os CLAUDE.md is an instructions file published in the GitHub repository ludeo-labs/cosmos-os (3 stars, last pushed 1mo ago), licensed MIT. It adds 441 tokens to every session, about $0.0022 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

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

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

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

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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,735 tokens