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.
npx skills add tu11aa/squadrant --skill add-pick-crew-rulegit clone --depth 1 https://github.com/tu11aa/squadrantWrote 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.
[](https://agentmods.dev/skills/tu11aa/squadrant/add-pick-crew-rule)<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>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.00901 |
| Opus 5 | $0.00022 | $0.00451 |
| Sonnet 5 | $0.00009 | $0.00180 |
| Haiku 4.5 | $0.00004 | $0.00090 |
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.
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
-
Read the current config:
cat ~/.config/squadrant/config.json -
Identify the
defaults.crewRouting.rulesarray. If it is absent, add it. -
Build the new rule object. Validate:
tieris a non-empty stringmatchis a valid regex (test it mentally against a sample task string)agentis one ofclaude,codex,gemini,opencodemodelis only set for claude rules (opusorsonnet); omit for other agents
-
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.
-
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". -
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'); "
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.
- 8d ago First seen · 89 lines · 43 tokens per session scan A b6ec09de2c77
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…