What is add-pick-crew-rule?

A configuration helper for managing crew routing rules in Squadrant, a tool that sends tasks to different AI agents and models. It lets you add, change, or remove keyword-based rules without editing JSON by hand.

Use it to route tasks such as difficult or routine work to selected agents and models by matching words or patterns in the task text.

It reduces mistakes when changing structured configuration and helps keep rule order correct, since the first matching rule is used.

add-pick-crew-rule — Skill for Claude Code by tu11aa/squadrant

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.

Any agent

npx skills add tu11aa/squadrant --skill add-pick-crew-rule

Clone the repo

git clone --depth 1 https://github.com/tu11aa/squadrant

Made for: Claude Code.

Or install squadrant, the plugin that ships this one along with the rest of its 27 skills.

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/skills/tu11aa/squadrant/add-pick-crew-rule/github.svg)](https://agentmods.dev/skills/tu11aa/squadrant/add-pick-crew-rule)

Your own site

<a href="https://agentmods.dev/skills/tu11aa/squadrant/add-pick-crew-rule"><img src="https://agentmods.dev/badge/skills/tu11aa/squadrant/add-pick-crew-rule/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/skills/tu11aa/squadrant/add-pick-crew-rule"><img src="https://agentmods.dev/badge/skills/tu11aa/squadrant/add-pick-crew-rule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,296 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 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.00043	$0.01296
Opus 5.5	$0.00017	$0.00518
Sonnet 5.5	$0.00009	$0.00259
Haiku 4.5	$0.00004	$0.00130

Measured 1mo ago against content hash 641d65211f32, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

add-pick-crew-rule 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 1mo 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.

plugin/skills/add-pick-crew-rule/SKILL.md · 106 lines

How it starts

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

Manage Crew Routing Rules

Crew routing rules live in defaults.crewRouting.rules inside ~/.config/squadrant/config.json. Each rule has the shape:

{
  "tier":  "<label>",      // human label, e.g. "extreme" / "hard" / "daily"
  "match": "<regex>",      // case-insensitive regex tested against the task text
  "agent": "claude|codex|gemini|opencode",
  "model": "opus|sonnet|flash|<literal upstream id>",  // a squadrant alias or a literal
  "backend": "native|direct|proxy"   // optional; claude-only for direct/proxy
}

Rules are evaluated in order; the first match wins.

direct/proxy are claude-only; native is valid for any agent:

native (default) — the CLI's own auth; no router needed.
direct — point Claude at defaults.router.baseUrl directly (env injection lands in U3).
proxy — point Claude at the squadrant loopback shim (env injection lands in U3).

A rule with backend: "direct" or "proxy" requires defaults.router to be configured; otherwise the spawn fails with a hard error and squadrant config check flags it.

model may be either a squadrant alias (defined in defaults.router.models) or a literal upstream id. An alias expands per agent — e.g. flash → deepseek-v4.1-flash for claude, opencode-go/deepseek-v4.1-flash for opencode. A value that is not a defined alias is used verbatim, so existing configs keep working.

Adding a rule

Read the current config:
```
cat ~/.config/squadrant/config.json
```
Identify the defaults.crewRouting.rules array. If it is absent, add it.
Build the new rule object. Validate:
- tier is a non-empty string
- match is a valid regex (test it mentally against a sample task string)
- agent is one of claude, codex, gemini, opencode
- backend (optional) is one of native, direct, proxy; direct/proxy are claude-only and require defaults.router (only matters when agent is claude)
- model applies to claude/opencode (codex does not consume it): may be a squadrant alias (see defaults.router.models) or a literal upstream id; aliases expand per agent

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

1mo ago Changed · +17 lines 641d65211f32
2mo ago First seen · 89 lines · 43 tokens per session scan A b6ec09de2c77

Subscribe to this mod's changes

add-pick-crew-rule is a skill published in the GitHub repository tu11aa/squadrant (2 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,296 once invoked, about $0.0002 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.

Building agents

add-pick-crew-rule next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
add-pick-crew-ruletu11aa/squadrant	Skill	2	yesterday	MIT	A	43	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code