devteam-select

A DevTeam command for choosing which saved development plan becomes active.

In plain words
What is it for?
Use it to select a plan by number, partial name, or full ID before running the implementation command.
Why use it?
It prevents work from being applied to the wrong plan and checks whether the selected plan can be started or resumed.

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/michael-harris/devteam/devteam-select
Any agent
npx skills add michael-harris/devteam --skill devteam-select
Clone the repo
git clone --depth 1 https://github.com/michael-harris/devteam

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 792 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.00025 $0.00792
Opus 5 $0.00013 $0.00396
Sonnet 5 $0.00005 $0.00158
Haiku 4.5 $0.00003 $0.00079

Measured 2d ago against content hash 153ba9c13a44, 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.

skills/devteam-select/SKILL.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 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       [pending]
  TASK-002: Create theme context                [pending]
  TASK-003: Update components for theme         [pending]
  TASK-004: Add theme toggle UI                 [pending]

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 · 151 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 · 151 lines · 25 tokens per session scan A 153ba9c13a44

Subscribe to this mod's changes

devteam-select is a skill published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 792 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

hydra

Multi-agent orchestration framework for Claude Code. Automatically delegates tasks to cheaper, faster sub-agents (Haiku, Sonnet) while maintaining Opus-level quality through verification. Use when working on any coding task — Hydra activates automatically to route file exploration, test running, documentation, code…

AR6420/Hail_Hydra · 83 tokens

quality-stack

Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when…

joaquimscosta/arkhe-claude-plugins · 148 tokens

prototype

Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery. Use when user runs /prototype, asks to "prototype a UI", "mock up a component", "generate HTML mockups", "create UI variations", "design exploration", "quick UI concept", or wants to…

joaquimscosta/arkhe-claude-plugins · 118 tokens

lyra

Transform vague inputs into precision-optimized AI prompts for Claude, ChatGPT, Gemini, or other LLMs. Use when user mentions "optimize prompt", "improve prompt", "lyra", "prompt engineering", or needs help crafting effective AI prompts.

joaquimscosta/arkhe-claude-plugins · 56 tokens

taskfile-setup

Install Taskfile (task) and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file (includes) patterns based on project complexity. Use when user runs /devtools:taskfile-setup, mentions "taskfile…

joaquimscosta/arkhe-claude-plugins · 110 tokens

sops-add-key

Add a new machine's age public key to .sops.yaml and re-encrypt all files. Use for multi-machine setups. Use when user mentions "add key", "add machine", "sops add key", "new machine", "authorize machine", "share key", "add public key", "multi machine sops".

joaquimscosta/arkhe-claude-plugins · 72 tokens