Borrowing it
Nothing to install: this file belongs to Archstone-Romania/archstone. 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/Archstone-Romania/archstone/main/CLAUDE.mdgit clone --depth 1 https://github.com/Archstone-Romania/archstoneWrote 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/archstone-romania/archstone/claude-md)<a href="https://agentmods.dev/instructions/archstone-romania/archstone/claude-md"><img src="https://agentmods.dev/badge/instructions/archstone-romania/archstone/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.01315 | $0.01315 |
| Opus 5 | $0.00658 | $0.00658 |
| Sonnet 5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
archstone 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 6d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code and other coding agents working in this repository.
What this is
Archstone — a compiler for AI capabilities. A business describes what it can do once, in CDL (the Capability Definition Language); the compiler lowers that to a target-agnostic IR, and emitters generate what an agent needs. MCP today, other protocols as they arrive.
It is not an MCP server. It generates one, and that distinction is the product: change the protocol and you regenerate rather than rewrite.
Where development happens
This repository is the home of the core — CDL, the compiler, the IR, emitters, runtime, CLI, embedded SDK and provider adapters. Issues, pull requests, CI and releases belong here.
⚠️ Transitional, as of 2026-08-26. The move is ratified but has not run. Until it does, this repository still receives release snapshots from a private development repository, and a snapshot's tree replaces this one wholesale. A change merged here that is not also in the development tree is erased at the next release, silently. If you are an agent working for the maintainer, make core changes in the development repository, not here. If you are an outside contributor, open the PR here as
CONTRIBUTING.mdsays — it will be re-applied upstream by hand until the migration completes.
Planning material — product strategy, commercial artifacts, pricing, research — lives in a private repository and always will. What reaches this one is the work and the technical argument for it, never the commercial reasoning behind choosing it.
The hosted commercial product will live in its own separate repository and depend on
@archstone/* from npm. The core must never depend on it. That direction is permanent and is
the mechanical form of the open-core commitment in
docs/adr/0005-open-core-boundary-artifact-guarantee.md.
Branches
Every change goes through a branch and a pull request, including a one-line edit. Name the branch for what the task is, with one of exactly three prefixes:
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.
- 6d ago First seen · 106 lines · 1,315 tokens per session scan A 1d49b8db2435
archstone CLAUDE.md is an instructions file published in the GitHub repository Archstone-Romania/archstone (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,315 tokens to every session, about $0.0066 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
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.
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).
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).
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.
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.