metaswarm: Command for Claude Code

.claude/commands/start-task.md

start-task is a command for Claude Code from dsifry/metaswarm. It costs 0 tokens per session (1,852 once invoked), scanned A, original, MIT.

A command for choosing and starting an appropriate development workflow for a coding task. It checks for unfinished plans, gathers project guidance, and can review open pull-request comments before work begins.

In plain words
What is it for?
Use it at the start of a task to recover or create a plan, prime project knowledge, check relevant pull requests, and decide how to approach the work.
Why use it?
It reduces the chance of starting with missing project context, overlooking an interrupted plan, or ignoring feedback on existing code changes.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents; mentions Codex.

This is dsifry/metaswarm's own configuration. It tells Claude Code how to work on metaswarm itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything metaswarm configures →

Part of the metaswarm plugin — 14 skills, 16 commands, 2 hooks shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to dsifry/metaswarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dsifry/metaswarm/main/.claude/commands/start-task.md
Clone the repo
git clone --depth 1 https://github.com/dsifry/metaswarm

Made for: Claude Code.

Or install metaswarm, the plugin that ships this one along with the rest of its 14 skills, 16 commands, 2 hooks.

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 start-task

README.md
[![agentmods](https://agentmods.dev/badge/commands/dsifry/metaswarm/start-task/github.svg)](https://agentmods.dev/commands/dsifry/metaswarm/start-task)
Your own site
<a href="https://agentmods.dev/commands/dsifry/metaswarm/start-task"><img src="https://agentmods.dev/badge/commands/dsifry/metaswarm/start-task/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.

agentmods 80×15 button for start-task

Your own site · 80×15
<a href="https://agentmods.dev/commands/dsifry/metaswarm/start-task"><img src="https://agentmods.dev/badge/commands/dsifry/metaswarm/start-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,852 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.00000 $0.01852
Opus 5.5 $0.00000 $0.00741
Sonnet 5.5 $0.00000 $0.00370
Haiku 4.5 $0.00000 $0.00185

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

Security

Grade A, and why

start-task 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.

.claude/commands/start-task.md · 197 lines

How it starts

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

Start Task

Determine task complexity and use appropriate workflow for efficient development.

Usage

/start-task <task-description>

Steps

0. Pre-Task Checklist

Before starting any new task:

Context Recovery Check:

  • Check if .beads/plans/active-plan.md exists with status: in-progress
  • If YES: An interrupted execution exists. Ask user: "There's an active plan from a previous session. Resume it or start fresh?"
    • Resume → run bd prime --work-type recovery and pick up where execution stopped
    • Start fresh → mark the old plan as status: abandoned and proceed normally

Knowledge Priming (CRITICAL):

  • Run BEADS prime: bd prime --keywords "<task-keywords>" --work-type planning
  • Review MUST FOLLOW rules and GOTCHAS before proceeding
  • Note any relevant patterns or decisions that constrain the approach

PR Check:

  • Check if there are active PRs with pending comments
  • Ask: "Before we start the new task, should we check if there are any PR comments to address?"
  • If yes, run: gh pr list --author @me --state open
  • Check each PR for new CodeRabbit comments

0.5. External Tools Check (informational only — never blocks the task)

Check if external AI tools (Codex, Gemini) are available for cost savings and cross-model review:

  • Run the health check scripts to detect installed tools:
    command -v codex >/dev/null 2>&1 && echo "codex: available" || echo "codex: not found"
    command -v gemini >/dev/null 2>&1 && echo "gemini: available" || echo "gemini: not found"
    
  • If tools are detected but .metaswarm/external-tools.yaml does not exist: Suggest the user enable them:

    "External tools (Codex/Gemini) are installed but not configured. Run mkdir -p .metaswarm && cp templates/external-tools.yaml .metaswarm/ to enable cost-saving delegation."

  • If no tools are detected: Briefly mention they can be installed:

    "Optional: Install Codex and Gemini CLIs for cost savings and cross-model review — see templates/external-tools-setup.md."

  • If tools are configured and working: No message needed — proceed silently.

Read the full file on GitHub · 197 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. 1mo ago First seen · 197 lines · 0 tokens per session scan A 4478b3143c73

Subscribe to this mod's changes

start-task is a command published in the GitHub repository dsifry/metaswarm (421 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,852 tokens. 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.