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.
npx agentmods add instructions/penso/arbor/claude-mdgit clone --depth 1 https://github.com/penso/arborWhat 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 | $0.01620 | $0.01620 |
| Opus 5 | $0.00810 | $0.00810 |
| Sonnet 5 | $0.00324 | $0.00324 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
arbor 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides instructions for Claude Code when working in this repository.
Priorities
- Keep code simple, explicit, and maintainable.
- Fix root causes, avoid temporary band-aids.
- Preserve user changes, never revert unrelated edits.
Toolchain
This project uses a pinned Rust nightly toolchain: nightly-2025-11-30. All commands go through just recipes which apply the correct toolchain automatically.
Commands
- Format:
just format - Format check:
just format-check - Lint (clippy):
just lint - Test:
just test - Full CI suite:
just ci - Run app:
just run - Run HTTP daemon:
just run-httpd
Before Committing / Pushing
Always run these checks before committing and fix any issues:
just format— auto-fix formattingjust lint— must pass with zero warnings (-D warnings)just test— all tests must pass
If any check fails, fix the issue, then commit the fix.
Never skip just format or just lint before a commit, even for small changes.
Git Workflow
Conventional commits: feat|fix|docs|style|refactor|test|chore(scope): description
No Co-Authored-By trailers. Update README.md features list with feat commits.
Rust Rules
- Do not use
unwrap()orexpect()in non-test code. In test modules, use#[allow(clippy::unwrap_used, clippy::expect_used)]on the module. - Use clear error handling with typed errors (
thiserror/anyhowwhere appropriate). - Use
arbor_core::ResultExtandarbor_core::OptionExtfor.context()onResult<T, E>andOption<T>— prefer these over ad-hoc.map_err()with format strings. - Use
SessionIdandWorkspaceIdnewtypes fromarbor_core::idinstead of rawStringfor session/workspace identifiers. These are#[serde(transparent)]for wire compatibility. - Keep modules focused and delete dead code instead of leaving it around.
- Collapse nested
if/if letstatements when possible (clippycollapsible_if). - Never shell out to external CLIs (
gh,gitviaCommand::new, etc.) for GitHub API calls or operations that can be done with Rust crates. Useoctocrab,reqwest, or other Rust HTTP/API crates instead. The only acceptable use ofstd::process::Commandis where no Rust crate equivalent exists.
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.
- 2d ago First seen · 133 lines · 1,620 tokens per session scan A 6506a2dbb052
arbor CLAUDE.md is an instructions file published in the GitHub repository penso/arbor (809 stars, last pushed 2mo ago), licensed MIT. It adds 1,620 tokens to every session, about $0.0081 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.
Other instructions, from other repositories
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.
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).
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.
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.
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).
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.