crew-config

A command for viewing, changing, or resetting CodeCrew settings, including model tiers, default mode, and token budgets.

In plain words
What is it for?
Use `/crew config show`, `/crew config set`, or `/crew config reset` to manage the project's CodeCrew configuration.
Why use it?
It provides one place to inspect or adjust how CodeCrew runs tasks.

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-config
Clone the repo
git clone --depth 1 https://github.com/d3x293/code-crew
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 102 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.00026 $0.00102
Opus 5 $0.00013 $0.00051
Sonnet 5 $0.00005 $0.00020
Haiku 4.5 $0.00003 $0.00010

Measured 2d ago against content hash fdf3259cffa3, 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.

commands/crew-config.md · 13 lines

What it actually says

Invoke the codecrew:crew-config skill with the user's config subcommand.

Parse the subcommand:

  • /crew config show → Display current configuration
  • /crew config set <key> <value> → Update a setting
  • /crew config reset → Restore all defaults

Pass the full subcommand and arguments to the skill.

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 · 13 lines · 26 tokens per session scan A fdf3259cffa3

Subscribe to this mod's changes

crew-config is a command published in the GitHub repository d3x293/code-crew (13 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 102 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.