add-pick-crew-rule

add-pick-crew-rule is a skill for Claude Code from tu11aa/squadrant. It costs 43 tokens per session (901 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
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.
Why use it?
It reduces mistakes when changing structured configuration and helps keep rule order correct, since the first matching rule is used.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Codex; mentions OpenCode.

Part of the squadrant plugin — 18 skills shipped together

Good fit 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.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tu11aa/squadrant/add-pick-crew-rule
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 18 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.

agentmods badge for add-pick-crew-rule

README.md
[![agentmods](https://agentmods.dev/badge/skills/tu11aa/squadrant/add-pick-crew-rule.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.svg" alt="Measured on agentmods" 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 901 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.00901
Opus 5 $0.00022 $0.00451
Sonnet 5 $0.00009 $0.00180
Haiku 4.5 $0.00004 $0.00090

Measured 8d ago against content hash b6ec09de2c77, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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 · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 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"   // omit for codex/opencode (they use their own defaults)
}

Rules are evaluated in order; the first match wins.

Adding a rule

  1. Read the current config:

    cat ~/.config/squadrant/config.json
    
  2. Identify the defaults.crewRouting.rules array. If it is absent, add it.

  3. 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
    • model is only set for claude rules (opus or sonnet); omit for other agents
  4. Insert the rule at the correct position — rules are evaluated in order. Higher-priority / more specific tiers (e.g. "extreme") belong before broader ones (e.g. "hard"). Append low-priority catch-alls last.

  5. Write the updated config back via the existing save path:

    // The saveConfig helper in src/config.ts handles atomic write + newline.
    // If editing the live file directly, use JSON.stringify(config, null, 2) + "\n".
    
  6. Verify the rule fires as expected:

    # Quick smoke-test (no live crew spawned):
    node -e "
      const {loadConfig} = require(process.env.HOME + '/.config/squadrant/node_modules/...');
      // or just log the matching rule manually
      const rules = require(process.env.HOME + '/.config/squadrant/config.json')
        .defaults?.crewRouting?.rules ?? [];
      const task = 'YOUR TEST TASK HERE';
      const hit = rules.find(r => new RegExp(r.match,'i').test(task));
      console.log(hit ?? 'no match');
    "
    

Read the full file on GitHub · 89 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. 8d 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 901 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens