devteam-select

A command for choosing one saved development plan as the current plan. The selected plan becomes the one used by the separate implementation command.

In plain words
What is it for?
Use it to select a plan by number, partial name, or full identifier, then make it the active plan for implementation.
Why use it?
It prevents work from being applied to the wrong plan and checks whether the chosen plan is ready, already finished, archived, or failed.

Command

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 commands/michael-harris/devteam/devteam-select
Clone the repo
git clone --depth 1 https://github.com/michael-harris/devteam
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 693 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.00000 $0.00693
Opus 5 $0.00000 $0.00347
Sonnet 5 $0.00000 $0.00139
Haiku 4.5 $0.00000 $0.00069

Measured 2d ago against content hash 072a4f3a7550, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devteam-select 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 2d 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.

commands/devteam-select.md · 136 lines

How it starts

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

DevTeam Select Command

Command: /devteam:select

Select a plan to work on. The selected plan becomes the active plan for /devteam:implement.

Usage

/devteam:select 2                    # Select by number (from /devteam:list)
/devteam:select notifications        # Select by name (partial match)
/devteam:select feature-dark-mode    # Select by full plan ID

Your Process

Step 1: Identify Plan

By number:

/devteam:select 2

→ Look up plan #2 from index

By partial name:

/devteam:select dark

→ Search plans for "dark" in name/ID, confirm if multiple matches

By full ID:

/devteam:select feature-dark-mode

→ Direct lookup

Step 2: Validate Plan

Check plan status:

  • planned → Ready to start
  • in_progress → Can resume
  • complete → Warn user (can re-run but likely not needed)
  • archived → Ask to unarchive first
  • failed → Ask to reset circuit breaker

Step 3: Update Active Plan

# Update index.json
active_plan: feature-dark-mode

# Update pointer file
echo "feature-dark-mode" > .devteam/active-plan.txt

Step 4: Show Confirmation

✅ Selected plan: Dark Mode Support (feature-dark-mode)

Type: feature
Parent: project-taskmanager
Status: planned
Sprints: 1 total, 0 completed

Tasks:
  📋 TASK-001: Define dark mode color tokens
  📋 TASK-002: Create theme context
  📋 TASK-003: Update components for theme
  📋 TASK-004: Add theme toggle UI

Next steps:
  • /devteam:implement         Execute this plan
  • /devteam:plan         Modify the plan
  • /devteam:list         See all plans

Disambiguation

If partial match finds multiple plans:

/devteam:select mode

Output:

Multiple plans match "mode":

  1. feature-dark-mode (Dark Mode Support)
  2. feature-offline-mode (Offline Mode)

Enter number to select, or use full ID:
>

Error Cases

Plan not found:

❌ No plan found matching "xyz"

Available plans:
  1. Task Manager App (project)
  2. Push Notifications (feature)
  3. Dark Mode Support (feature)

Use /devteam:list to see all plans.

Read the full file on GitHub · 136 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. 2d ago First seen · 136 lines · 0 tokens per session scan A 072a4f3a7550

Subscribe to this mod's changes

devteam-select is a command published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 693 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.