crew-init

A project setup command for CodeCrew, a team of coding agents that work on a software project.

In plain words
What is it for?
It helps scan the codebase, identify its languages and frameworks, build searchable project indexes, create a project profile, configure agents, and select relevant skills.
Why use it?
It removes the need to inspect the project and configure the agent team by hand before delegating work.

Command

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 commands/d3x293/code-crew/crew-init
Clone the repo
git clone --depth 1 https://github.com/d3x293/code-crew
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 126 The whole file, excluding the scripts and references it only reads on demand.
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.00019 $0.00126
Opus 5 $0.00010 $0.00063
Sonnet 5 $0.00004 $0.00025
Haiku 4.5 $0.00002 $0.00013

Measured yesterday against content hash 7256915d6aa3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

crew-init 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 yesterday.

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.

commands/crew-init.md · 14 lines

What it actually says

Invoke the codecrew:crew-init skill to perform full project initialization:

  1. Scan the project structure, detect languages, frameworks, patterns
  2. Build the 3-layer codebase index (compact index + symbol map)
  3. Generate project profile (.claude/crew-profile.md)
  4. Auto-configure the agent team based on detected stack
  5. Build the skill catalog with relevant skills pre-selected

Pass any arguments the user provided (e.g., specific directories to focus on).

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. yesterday First seen · 14 lines · 19 tokens per session scan A 7256915d6aa3

Subscribe to this mod's changes

crew-init is a command published in the GitHub repository d3x293/code-crew (13 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 126 once invoked, about $0.0001 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.