command-ops

An on-demand operations procedure for Squadrant, the system that coordinates work across projects and coding-agent sessions. It handles briefings, delegation, project registration, status checks, and reviews of recorded learnings.

In plain words
What is it for?
Use it for a daily briefing, delegating work, registering a project, checking project status, or reviewing learnings.
Why use it?
It gives routine coordination work a consistent process and lets each command task finish and exit instead of running continuously.

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/tu11aa/squadrant/command-ops
Any agent
npx skills add tu11aa/squadrant --skill command-ops
Clone the repo
git clone --depth 1 https://github.com/tu11aa/squadrant

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,548 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.00048 $0.01548
Opus 5 $0.00024 $0.00774
Sonnet 5 $0.00010 $0.00310
Haiku 4.5 $0.00005 $0.00155

Measured yesterday against content hash 54afadaf6f29, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

command-ops 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 yesterday.

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/command-ops/SKILL.md · 150 lines

How it starts

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

Command Operations

On-demand only. Command is no longer launched by squadrant launch --all. You were spawned by squadrant command --task <briefing|learnings-review|wiki-aggregate> to run a single task and exit. Do the task, then exit cleanly — no persistent loop.

Daily Briefing (Session Start)

Run when session starts, or user says "morning", "catch up", "summary":

  1. Check handoffs from all projects (context from yesterday's sessions):
for vault in $(cat ~/.config/squadrant/config.json | python3 -c "import json,sys; [print(p['spokeVault']) for p in json.loads(sys.stdin.read())['projects'].values()]"); do
  echo "=== $(basename $vault) ==="
  ~/.config/squadrant/scripts/read-handoff.sh "$vault" --keep
done

Handoffs contain: currentState, openBranches, nextSteps, blockedItems, decisions. Use these to understand where each project left off.

  1. Search claude-mem (mem-search skill) for recent activity across all projects.
  2. Read yesterday's logs:
YESTERDAY=$(date -v-1d +"%Y-%m-%d")
for vault in $(cat ~/.config/squadrant/config.json | python3 -c "import json,sys; [print(p['spokeVault']) for p in json.loads(sys.stdin.read())['projects'].values()]"); do
  echo "=== $vault ==="
  cat "$vault/daily-logs/${YESTERDAY}.md" 2>/dev/null || echo "(no log)"
done
  1. Run quick standup for context: squadrant standup --yesterday --raw
  2. Present briefing, then save to {hubVault}/daily-logs/YYYY-MM-DD.md

Delegation Workflow

When the user gives a task for a project:

1. Identify project

Match to ~/.config/squadrant/config.json.

2. Check for captain workspace

squadrant runtime list

CRITICAL: Match the EXACT captainName from config. Brove⚓ brove-captain.

3. Freshness gate (run BEFORE deciding to reuse)

A name match is not sufficient — the workspace may be holding a session from a previous day. Check sessions.json against today before reusing:

TODAY=$(date +%Y-%m-%d)
LAST=$(python3 -c "import json; d=json.load(open('$HOME/.config/squadrant/sessions.json')); print(d.get('workspaces',{}).get('{captainName}',{}).get('lastLaunched',''))" 2>/dev/null)
[ "$LAST" = "$TODAY" ] && echo "fresh" || echo "stale"
  • fresh → reuse the existing workspace, proceed to step 5.
  • stale (or no entry) → close the existing workspace, then go to step 4 to respawn so spawn-workspace.sh runs its ↻ new day — starting fresh session path:
    squadrant runtime stop <project>
    

Read the full file on GitHub · 150 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. yesterday First seen · 150 lines · 48 tokens per session scan A 54afadaf6f29

Subscribe to this mod's changes

command-ops is a skill published in the GitHub repository tu11aa/squadrant (2 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,548 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

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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 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