crew-config

A configuration manager for CodeCrew, the multi-agent coding system. It stores settings such as operating mode, model choices, agent activation, token budgets, automatic indexing, and history limits.

In plain words
What is it for?
Use it to view, change, or reset CodeCrew settings, including full or lite mode, automatic indexing, model overrides, agent overrides, and execution limits.
Why use it?
It lets you change how CodeCrew behaves without manually editing its JSON configuration file.

Skill for Claude CodeCodex

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 skills/d3x293/code-crew/crew-config
Any agent
npx skills add d3x293/code-crew --skill crew-config
Clone the repo
git clone --depth 1 https://github.com/d3x293/code-crew

Made for: Claude Code, Codex.

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 799 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.00034 $0.00799
Opus 5 $0.00017 $0.00400
Sonnet 5 $0.00007 $0.00160
Haiku 4.5 $0.00003 $0.00080

Measured 2d ago against content hash d04c8c151c6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

crew-config 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.

skills/crew-config/SKILL.md · 95 lines

How it starts

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

Crew Config - User Configuration Manager

Reads and writes .claude/crew-config.json to customize CodeCrew behavior.

When to Activate

  • User runs /crew config show|set|reset
  • Other skills check for config overrides at startup

Config File

Location: .claude/crew-config.json (created on first set command)

Default values (used when file doesn't exist):

{
  "defaultMode": "full",
  "modelOverrides": {},
  "agentOverrides": {},
  "tokenBudgets": {
    "opus": 3000,
    "sonnet": 2000,
    "sonnet-planner": 2500,
    "haiku": 800
  },
  "autoIndex": true,
  "historyLimit": 50
}

Subcommands

show — Display Current Configuration

  1. Read .claude/crew-config.json (if exists, otherwise show defaults)
  2. Display:
Config: Mode={full|lite} | Auto-Index={on|off} | History={count}
Budgets: Opus {t}tk/{s}sk | Sonnet {t}tk/{s}sk | Sonnet-planner {t}tk/{s}sk | Haiku {t}tk/{s}sk
Model overrides: {none | list}
Agent overrides: {none | list}

set <key> <value> — Update a Setting

Supported keys:

Key Values Example
mode full, lite /crew config set mode lite
auto-index true, false /crew config set auto-index false
history-limit number /crew config set history-limit 100
agent.<name>.model opus, sonnet, haiku /crew config set agent.senior-dev.model opus
agent.<name>.active true, false /crew config set agent.security-analyst.active true
budget.<tier> number (tokens) /crew config set budget.sonnet 2500

Process:

  1. Read existing .claude/crew-config.json (or start with defaults)
  2. Validate the key and value
  3. Apply the change
  4. Write back to .claude/crew-config.json
  5. Confirm: "Set {key} = {value}"

Validation rules:

  • mode: must be full or lite
  • agent.<name>.model: agent must exist in crew-team.json
  • budget.<tier>: must be a positive number, max 5000
  • Warn if user sets a Haiku agent to Opus (expensive, possible but discouraged)

Read the full file on GitHub · 95 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. 2d ago First seen · 95 lines · 34 tokens per session scan A d04c8c151c6b

Subscribe to this mod's changes

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