Borrowing it
Nothing to install: this file belongs to coltonbearden/carrel. 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/coltonbearden/carrel/main/CLAUDE.mdgit clone --depth 1 https://github.com/coltonbearden/carrelWrote 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/coltonbearden/carrel/claude-md)<a href="https://agentmods.dev/instructions/coltonbearden/carrel/claude-md"><img src="https://agentmods.dev/badge/instructions/coltonbearden/carrel/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.
<a href="https://agentmods.dev/instructions/coltonbearden/carrel/claude-md"><img src="https://agentmods.dev/badge/instructions/coltonbearden/carrel/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01328 | $0.01328 |
| Opus 5.5 | $0.00531 | $0.00531 |
| Sonnet 5.5 | $0.00266 | $0.00266 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
carrel 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 17d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project CLAUDE.md — Local File Toolkit + Plugin Marketplace
Resume from disk: read STATE.md first — it always says what's done, what's in flight, and what's next. Decisions live in docs/DECISIONS.md.
Product name — single source of truth
The product name, tagline, and version live ONLY in product.json at the repo root. Never hardcode the name in code. Docs/manifests may use the name in prose, but anything generated (CLI banner, --version, asset text) must read product.json. Do not run scripts/finalize.sh: it was for the original hand-off only (it relocates the tree and creates a new repo; STATE.md).
Stack & layout
- Python ≥3.12 (dev box: 3.14), managed by uv (
pyproject.toml,uv run,uv sync). - Core library in
src/carrel/; umbrella CLI entry inpyproject.toml [project.scripts]. - All external binaries are called through the single adapter layer
src/carrel/core/adapters.py— neversubprocessdirectly from command modules. Adapters do capability detection and convert timeouts into a clean error. One documented exception:core/actions.pyruns the user-authored--runshell actions ofwatchandbatch(shell-quoted substitutions,--action-timeout; D-013). - Repo root doubles as a Claude Code plugin marketplace:
.claude-plugin/marketplace.json+plugins/<name>/.
Coding standards
- Python: type hints on public functions,
pathlib.Pathover strings, no global state, f-strings, stdlibargparse-free — we use the CLI framework chosen in Phase 2 (see docs/ARCHITECTURE.md). - Every CLI command MUST have: working
--help,--jsonflag when output is data, ≥1 test, graceful degradation when an optional binary is missing (actionable message + install hint, exit code 3 — never a traceback, never a silent no-op). - No stubs/TODO/placeholder code in shipped commands. Cut and document in
docs/FEATURES.mdinstead. - Wrap, don't rewrite: prefer proven libraries/binaries via the adapter layer; attribute in docs/LICENSES section.
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.
- 17d ago Changed · +1 lines · +117 tokens per session 06fcb440faa8
- 1mo ago Changed · +10 tokens per session b6289be8300f
- 1mo ago Changed · +21 lines · +301 tokens per session 84928a5f8d4f
- 1mo ago Changed · +4 lines · +208 tokens per session 8b2d6c2d9f8d
- 1mo ago First seen · 45 lines · 692 tokens per session scan A 748f7baf1790
carrel CLAUDE.md is an instructions file published in the GitHub repository coltonbearden/carrel (2 stars, last pushed 2d ago), licensed MIT. It adds 1,328 tokens to every session, about $0.0053 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.
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).
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.
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).
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 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.