What is crew CLAUDE.md?

Repository instructions for crew, a package manager for Agent Skills. A package manager installs and manages reusable instructions that coding agents can load for specific tasks.

They guide changes to commands, flags, errors, configuration, file formats, defaults, supported agent connections, and conformance rules. They also distinguish those changes from refactoring and test updates.

They tell contributors which changes affect the project’s formal product requirements and which are only internal implementation work. This keeps the documented contract and the implementation aligned.

How with-logic/crew configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to with-logic/crew. 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/with-logic/crew/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/with-logic/crew

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/with-logic/crew/claude-md/github.svg)](https://agentmods.dev/instructions/with-logic/crew/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/with-logic/crew/claude-md"><img src="https://agentmods.dev/badge/instructions/with-logic/crew/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/with-logic/crew/claude-md"><img src="https://agentmods.dev/badge/instructions/with-logic/crew/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 7,794 This file is loaded in full into every session.

When invoked 7,794 The same file — it is already loaded in full.

Security scan C 2 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.

Model	Per session	Once invoked
Fable 5.1	$0.07794	$0.07794
Opus 5.5	$0.03118	$0.03118
Sonnet 5.5	$0.01559	$0.01559
Haiku 4.5	$0.00779	$0.00779

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

Security

Grade C, and why

crew CLAUDE.md scanned grade C with 2 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 16d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

doesn't regenerate cleanly. Prefer `rm -rf coverage/ && bun test` to

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- **Don't mock `git`** at the `Bun.spawnSync` level. Use the

CLAUDE.md · 671 lines

How it starts

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

crew — Contributor Guide

This file is the briefing for anyone (human or AI) working on crew. Read it before making changes.

crew is a package manager for Agent Skills specified by PRD.md. The PRD is the contract; this document is about how we implement it.

Working agreement: specification changes

If you are asked to make a change that is not specific to our implementation — that is, a change that any conformant implementation of the spec would also need to make — update PRD.md first.

Examples of what triggers a PRD update:

A new command, flag, or subcommand.
A new error name or a change to an exit code.
A change to the marker format, state schema, or config schema.
A change to the reference grammar or resolution precedence.
A change to a default (tap URL, autoupdate interval, lock timeout, …).
A change to the hash algorithm or what it covers.
Adding, removing, or renaming an agent adapter (the set in §7.2).
A change that shifts any of the §18 conformance criteria.

Examples of what does not need a PRD update:

Internal refactors, file moves, renamed internal functions.
Test additions or helper tweaks.
Dependency bumps that don't change behavior.
Bug fixes that make behavior match the existing spec.
Performance improvements within existing guarantees.

When in doubt: if an external observer running the conformance suite could notice the change, update the PRD. The PRD is what a second implementation would read to build the same tool — keep it accurate.

After updating the PRD, update src/ and tests/ to match. Don't leave a PRD change unimplemented across a commit.

Working agreement: user-facing surfaces

If a change affects user-visible behavior — a new command, a new flag, a change to install/update/tap semantics, a new way for a tap to be structured, a renamed default, anything a user of the CLI would notice — also check whether these user-facing surfaces describe the thing you just changed, and keep them in sync:

Read the full file on GitHub · 671 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.

16d ago Changed · -2 lines · -53 tokens per session ce9dcd401fc9
21d ago Changed · +4 lines · +85 tokens per session 0737b09b3cb2
1mo ago Changed · +36 lines · +523 tokens per session 03968522992a
1mo ago Changed · +4 lines · +78 tokens per session 6f0a5fce0cc6
2mo ago First seen · 629 lines · 7,161 tokens per session scan C abd1374efab0

Subscribe to this mod's changes

crew CLAUDE.md is an instructions file published in the GitHub repository with-logic/crew (48 stars, last pushed 5d ago), licensed MIT. It adds 7,794 tokens to every session, about $0.0312 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

crew CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
crew CLAUDE.mdwith-logic/crew	Instructions file	48	5d ago	MIT	C	7,794	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

crew: Instructions file for Claude Code