agentstack: Instructions file for Claude Code

CLAUDE.md

agentstack CLAUDE.md is an instructions file for Claude Code from Tarekkharsa/agentstack. It costs 562 tokens per session, scanned A, original, Apache-2.0.

Project instructions for AgentStack, a Rust workspace that governs how coding agents use trust, policy, runtime, recording, import, rendering, and restore code. A workspace is a repository containing related packages that are built together.

In plain words
What is it for?
Use them when modifying AgentStack to find the authoritative strategy, work queue, architecture, enforcement rules, and package boundaries, and to guide Rust implementation choices.
Why use it?
They help contributors extend existing code safely and keep enforcement in the command-line interface instead of duplicating or bypassing established paths.

Instructions file for Claude Code

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tarekkharsa/agentstack/claude-md"><img src="https://agentmods.dev/badge/instructions/tarekkharsa/agentstack/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 562 This file is loaded in full into every session.
When invoked 562 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.00562 $0.00562
Opus 5.5 $0.00225 $0.00225
Sonnet 5.5 $0.00112 $0.00112
Haiku 4.5 $0.00056 $0.00056

Measured 2mo ago against content hash f1b7d77b08de, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agentstack 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 2mo 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 · 52 lines

How it starts

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

CLAUDE.md — AgentStack

Shipped Rust workspace. Extend existing seams; do not reimplement working trust, policy, gateway, runtime, recording, import, render, or restore paths. Prefer clear, boring, idiomatic Rust; explain non-obvious ownership/lifetime/ trait/error choices briefly.

crates/
  core/       manifest, lockfile, digests
  trust/      content-bound consent and signatures
  policy/     machine-first policy intersection
  adapters/   native config compilers for supported CLIs
  recorder/   call and run evidence
  runtime/    sandbox orchestration
  egress/     enforced network proxy
  executor/   policy-agnostic governed execution domain
  workflow/   self-contained Boa workflow engine
  mcp/        MCP protocol boundary, RMCP confined behind a JSON backend
  cli/        binary, orchestration, JSON/action APIs

Authorities: STRATEGY.md (strategy), TODO.md (the only work queue), docs/ARCHITECTURE.md + docs/ENFORCEMENT.md (what the code does and enforces). docs/archive/ is history, never direction. The CLI is the primary surface and source of authority; t3code is an optional companion calling stable read APIs and fixed actions, never an enforcement boundary. Never recreate a second UI.

Invariants

The non-negotiable invariants live in STRATEGY.md ("What never changes") and docs/ENFORCEMENT.md; every change must preserve them. Hooks always get the full consent ceremony; trust and policy stay small review boundaries; new dependencies need maintainer approval; Boa stays isolated in workflow.

Hard rules — context and tests

  • Never run the full test suite locally. Loop: cargo check -p <crate> while iterating; cargo test -p <crate> (or --test <name>) only for crates the change can break; full suite belongs to CI.
  • Before handoff: cargo check --workspace --all-targets (the only cheap check that sees all test targets), cargo fmt --check, relevant clippy.

Hard rules — build cache

  • Building in .claude/worktrees/*: export CARGO_TARGET_DIR="$HOME/.cache/agentstack-target" first, so every worktree shares one incremental cache instead of recompiling the workspace per tree.
  • Debug builds by default; --release only when CI parity demands it.
  • Removing a worktree: delete its local target/ with it.

Read the full file on GitHub · 52 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. 2mo ago First seen · 52 lines · 562 tokens per session scan A f1b7d77b08de

Subscribe to this mod's changes

agentstack CLAUDE.md is an instructions file published in the GitHub repository Tarekkharsa/agentstack (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 562 tokens to every session, about $0.0022 per session on Opus 5.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 · 9,715 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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 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 · 4,261 tokens