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.
npx agentmods add skills/michael-harris/devteam/devteam-implementnpx skills add michael-harris/devteam --skill devteam-implementgit clone --depth 1 https://github.com/michael-harris/devteamWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00022 | $0.03685 |
| Opus 5 | $0.00011 | $0.01843 |
| Sonnet 5 | $0.00004 | $0.00737 |
| Haiku 4.5 | $0.00002 | $0.00368 |
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.
How it starts
The opening of the file, as written. The whole thing — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Current session: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_current_session 2>/dev/null || echo "No active session"
Active sprint: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_kv_state "active_sprint" 2>/dev/null || echo "None"
Failure count: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_kv_state "consecutive_failures" 2>/dev/null || echo "0"
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 "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh"
source "${CLAUDE_PLUGIN_ROOT}/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
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.
- yesterday First seen · 550 lines · 0 tokens per session scan A 9e1161b8c201
devteam-implement is a skill published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 3,685 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.
Other skills, from other repositories
find-opps
Find new directions for an ops project — adjacent opportunities, strategic gaps, preparatory research. Use when known work is well-mined and you need to look outward.
prioritize
Pick 2–3 independent ops tasks from active plans and backlog for autonomous execution, weighing impact, feasibility, and project goals.
plan
Create an ops work plan for a new task. Proposes steps and success criteria for user approval before execution.
raindrop-triage
This skill should be used when the user asks to 'triage unsorted bookmarks', 'clean up raindrop inbox', 'sort unsorted', 'organize bookmarks', 'raindrop triage', 'process bookmark backlog', 'promote triaged bookmarks', 'classify triaged', 'raindrop cleanup', 'deduplicate bookmarks', 'find duplicate bookmarks', 'tag…
upstream-tracker
Manage upstream issue tracking for this project. Use when the user wants to log a bug or friction point in a vendor package or npm dependency, review open upstream items, resolve a tracked issue, run a trend review, generate the upstream observations section of a sprint retrospective, promote upstream observations to…
retrospective
Run a sprint retrospective for this project. Use when the user says 'retrospective', 'retro', 'close out the sprint', 'what went well', 'generate retro', or wants to generate a RETRO-NN.md file. Reads UPSTREAM-.md files, recent git history, and conversation context to pre-populate the retrospective. Do NOT use for…