agentmods.dev

strata-core CLAUDE.md

Project instructions for Strata-Core, including its current V1 architecture, Rust workspace rules, package names, storage layout, and boundaries between system layers.

In plain words
What is it for?
Use them when changing Strata-Core crates, storage or engine behavior, database compatibility, versioning, publishing settings, or the V1 integration flow.
Why use it?
They prevent agents from reviving retired code or adding compatibility paths that conflict with the project’s current design.

Instructions file

2 3d ago A scan 2,900 tokens original Apache-2.0
View the source file stratalab/strata-core
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/stratalab/strata-core/claude-md
Clone the repo
git clone --depth 1 https://github.com/stratalab/strata-core
Per session 2,900 This file is loaded in full into every session.
When invoked 2,900 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.02900 $0.02900
Opus 5 $0.01450 $0.01450
Sonnet 5 $0.00580 $0.00580
Haiku 4.5 $0.00290 $0.00290

Measured 2d ago against content hash 486e5fa30034, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

strata-core 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 2d 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 · 243 lines

How it starts

The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Strata-Core: Claude Code Instructions

Status

The V1 architecture is the product. main carries the V1 line; the v1 integration branch has been promoted and retired. Pre-V1 code exists only in git history — do not resurrect it.

Workspace version is 1.0.0, inherited from [workspace.package]. Publish names are decided: stratadb (embedded-library facade crate) and strata-cli (the strata binary). All crates remain publish = false until the release train lands.

The V1 line is a clean break. No compatibility shims between old and new code, no migration tooling for pre-V1 databases, no parallel old/new paths held alive indefinitely. Opening a pre-V1 database directory fails with failed_precondition.engine.layout_version.

V1 Stack

core
  → storage
  → engine
  → intelligence → executor / CLI / SDK / Strata AI
  → inference
  • core — smallest shared atoms (BranchId, CommitVersion, timestamp, type-local validation errors). No Value, no EntityRef, no storage transaction IDs.
  • storage — generic persistence mechanics, L1-L9 layered. Knows nothing about KV/JSON/event/vector/graph semantics.
  • engine — product semantics, data capabilities, branches, time travel, retrieval, IPC classification, clone artifacts, derived-state manifests. Owns adapter traits used by intelligence.
  • intelligence — autoembedding, query expansion, reranking, RAG, generation orchestration. Consumes engine surfaces; never imports storage; never speaks provider HTTP.
  • inference — provider execution and model artifact resolution. Generator / Embedder / Reranker traits. Knows nothing about Strata databases.
  • executor / CLI / SDK / Strata AI — consume engine and intelligence. Never import storage directly. Never import inference directly.

Where To Read Before Working On A Slice

  1. Roadmap — docs/architecture/strata-v1-implementation-roadmap.md
  2. Current milestone plan — docs/architecture/implementation-plans/m{N}-m{N}t-implementation-plan.md
  3. Layer architecture — docs/architecture/{layer}-architecture.md
  4. Contracts — docs/architecture/engine/<contract>.md or docs/architecture/storage/<layer>.md (docs keep their design-phase names)
  5. Test inventory — docs/architecture/v1-existing-test-inventory-and-porting-plan.md
  6. Engineering standards — docs/architecture/v1-engineering-standards.md
  7. Error contract — docs/architecture/v1-error-and-diagnostics-contract.md
  8. Storage format spec — docs/spec/strata-storage-format-v1.md
  9. Adding/changing a command — crates/executor/idl/v1/README.md (the IDL runbook: authored files, regenerate/verify sequence, coverage guards, SDK wiring)

Read the full file on GitHub · 243 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. 2d ago First seen · 243 lines · 2,900 tokens per session scan A 486e5fa30034

Subscribe to this mod's changes

strata-core CLAUDE.md is an instructions file published in the GitHub repository stratalab/strata-core (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 2,900 tokens to every session, about $0.0145 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

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

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

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,182 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,345 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

next.js 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