devteam-implement

A command for carrying out planned or one-off development work. It can execute a selected task, sprint, plan, or all sprints in sequence.

In plain words
What is it for?
Use it for tasks such as adding pagination, fixing a typo, auditing authentication, or restructuring utility code. A sprint is a grouped set of development tasks.
Why use it?
It gives you one way to start implementation work while handling task selection and, for unclear requests, an ambiguity check.

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-implement
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 3,925 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.03925
Opus 5 $0.00000 $0.01962
Sonnet 5 $0.00000 $0.00785
Haiku 4.5 $0.00000 $0.00392

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

Security

Grade A, and why

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

commands/devteam-implement.md · 572 lines

How it starts

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

DevTeam Implement Command

Command: /devteam:implement [task] [options]

Execute implementation work - plans, sprints, tasks, or ad-hoc work.

Usage

# Execute selected/current plan
/devteam:implement

# Execute specific sprint
/devteam:implement --sprint 1
/devteam:implement --sprint SPRINT-001

# Execute all sprints
/devteam:implement --all

# Execute specific task
/devteam:implement --task TASK-001

# Ad-hoc task (will trigger interview if ambiguous)
/devteam:implement "Add pagination to user list"

# Cost-optimized execution
/devteam:implement --eco
/devteam:implement --sprint 1 --eco

# Skip interview for ad-hoc tasks
/devteam:implement "Fix typo in header" --skip-interview

# Specify task type for better agent selection
/devteam:implement "Audit auth flow" --type security
/devteam:implement "Restructure utils" --type refactor

Options

Option Description
--sprint <id> Execute specific sprint
--all Execute all sprints sequentially
--task <id> Execute specific task
--eco Cost-optimized execution (slower escalation, summarized context)
--skip-interview Skip ambiguity check for ad-hoc tasks
--type <type> Specify task type: feature, bug, security, refactor, docs
--model <model> Force starting model: haiku, sonnet, opus
--max-iterations <n> Override max iterations (default: 10)
--show-worktrees Debug: Show worktree operations (normally hidden)

Your Process

Phase 0: Initialize Session

# Source state management
source scripts/state.sh
source scripts/events.sh

# Start session
SESSION_ID=$(start_session "/devteam:implement $*" "implement")
log_session_started "/devteam:implement $*" "implement"

# Determine execution mode
if [[ "$*" == *"--eco"* ]]; then
    set_state "execution_mode" "eco"
fi

Create/update session in database:

INSERT INTO sessions (
    id, command, command_type, execution_mode, status, current_phase
) VALUES (
    'session-xxx', '/devteam:implement --sprint 1', 'implement', 'normal', 'running', 'initializing'
);

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

Subscribe to this mod's changes

devteam-implement 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 3,925 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.