cli CLAUDE.md

A set of repository instructions for the Archcore CLI, its server, integrations and document templates. It explains where to look for project guidance and how to handle Archcore documents.

In plain words
What is it for?
It is for work involving technical documentation, CLI features, MCP tools, hooks, agents and files in the .archcore directory.
Why use it?
It helps coding agents follow the repository's required search order, writing rules and document-management process.

Instructions file

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/archcore-ai/cli/claude-md
Clone the repo
git clone --depth 1 https://github.com/archcore-ai/cli
Per session 1,528 This file is loaded in full into every session.
When invoked 1,528 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.01528 $0.01528
Opus 5 $0.00764 $0.00764
Sonnet 5 $0.00306 $0.00306
Haiku 4.5 $0.00153 $0.00153

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

Security

Grade A, and why

cli 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 · 162 lines

How it starts

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

CLAUDE.md

Read and follow AGENTS.md before creating or editing technical documentation, Archcore documents, CLI help, MCP tool descriptions, prompts, agent instructions, or user-facing Markdown.

The writing policy in AGENTS.md applies two profiles: an ASD-STE100-inspired profile constrains the sentence, and an ISO 24495-1-inspired profile constrains the structure. The document type decides which half binds. The per-type assignment — profile, line format, and metric — lives in the shared Archcore rule concepts/document-prose-canon.

Do not claim formal ASD-STE100 or ISO 24495-1 compliance.

Search Priority

When researching patterns, decisions, or conventions in this project, always search .archcore/ documents first (list_documentsget_document) before grepping the codebase or using external sources.

The canonical architecture and how-to reference is .archcore/cli-ui/building-the-cli.doc.md. Consult it before adding a command, document type, MCP tool, hook, or agent.

Archcore Operations

Use Archcore MCP tools for all .archcore/ document operations.

  • Create documents with create_document.
  • Update documents with update_document.
  • Remove documents with remove_document.
  • Read documents with list_documents, search_documents, and get_document.
  • Manage document relations with add_relation, remove_relation, and list_relations.

Do not use direct file-writing tools to modify .archcore/ documents.

Before creating or updating an Archcore document:

  1. Search existing documents for relevant decisions, rules, specifications, and duplicates.
  2. Read the applicable document-type guidance.
  3. Apply the controlled technical writing policy in AGENTS.md.
  4. Preserve code identifiers, commands, flags, paths, MCP tool names, configuration keys, and literal values exactly.
  5. Mark unsupported technical claims with [assumption].

Treat mounted global documents as read-only. Do not edit them or create relations to them.

Managed Blocks

Read the full file on GitHub · 162 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 · 162 lines · 1,528 tokens per session scan A 80a2f81513c7

Subscribe to this mod's changes

cli CLAUDE.md is an instructions file published in the GitHub repository archcore-ai/cli (62 stars, last pushed 16d ago), licensed Apache-2.0. It adds 1,528 tokens to every session, about $0.0076 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.