devteam-list

A command that lists development plans and shows their type, status, and progress. A development plan is a tracked set of tasks for a project or feature.

In plain words
What is it for?
Use it to list all plans, include archived plans, or filter plans by type.
Why use it?
It gives you a quick view of active, planned, completed, or archived work without opening each plan separately.

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

Made for: Claude Code, Codex.

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 832 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.00012 $0.00832
Opus 5 $0.00006 $0.00416
Sonnet 5 $0.00002 $0.00166
Haiku 4.5 $0.00001 $0.00083

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

Security

Grade A, and why

devteam-list 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.

skills/devteam-list/SKILL.md · 124 lines

How it starts

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

Session state: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_current_session 2>/dev/null || echo "No active session" Recent events: !sqlite3 .devteam/devteam.db "SELECT type, message FROM events ORDER BY created_at DESC LIMIT 10" 2>/dev/null || echo "No events"

DevTeam List Command

Command: /devteam:list

List all development plans and their status.

Usage

/devteam:list                    # Show all plans
/devteam:list --all              # Include archived plans
/devteam:list --type feature     # Filter by type

Your Process

Step 1: Read Plan Index

# Load plan index
cat .devteam/plans/index.json

If no index exists:

No plans found.

Create a new plan with:
  /devteam:plan "Project description"

Or create a feature plan:
  /devteam:plan --feature "Feature description"

Step 2: Display Plan List

DEVELOPMENT PLANS

Active: feature-notifications

 #  | Name                 | Type    | Status      | Progress
 1  | Task Manager App     | project | complete    | 5/5
 2  | Push Notifications   | feature | active      | 1/2       <- ACTIVE
 3  | Dark Mode Support    | feature | planned     | 0/1

Commands:
  /devteam:select <#>     Select a plan to work on
  /devteam:implement           Execute the active plan
  /devteam:plan --feature Create new feature plan

Status Icons

Icon Status Meaning
planned planned Plan created, not started
active in_progress Currently being executed
complete complete All sprints finished
paused paused Execution paused
failed failed Circuit breaker triggered
archived archived Moved to archive

With --all Flag

Include archived plans:

DEVELOPMENT PLANS (including archived)

Active Plans:
 #  | Name                 | Type    | Status      | Progress
 1  | Task Manager App     | project | complete    | 5/5
 2  | Push Notifications   | feature | active      | 1/2
 3  | Dark Mode Support    | feature | planned     | 0/1

Archived Plans:
 4  | Old Dashboard        | feature | archived    | 2/2
 5  | Cancelled Auth       | feature | archived    | 0/3

Read the full file on GitHub · 124 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 · 124 lines · 0 tokens per session scan A ce0181501c7d

Subscribe to this mod's changes

devteam-list is a skill published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 832 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