team-lead

team-lead is an agent for Claude Code from alinaqi/maggy. It costs 26 tokens per session (611 once invoked), scanned A, original, MIT.

A team-coordination agent that organizes software work across multiple feature agents. It creates tasks, assigns dependencies, monitors progress, and handles blockers.

In plain words
What is it for?
Reading feature specifications, checking for duplicates, creating linked tasks, assigning specification and implementation work, monitoring agents, and closing the team after delivery.
Why use it?
It gives larger projects a structured task chain so related work happens in the right order and shared files are coordinated.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Good fit Reading feature specifications, checking for duplicates, creating linked tasks, assigning specification and implementation work, monitoring agents, and closing the team after delivery.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alinaqi/maggy/team-lead
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.

Clone the repo
git clone --depth 1 https://github.com/alinaqi/maggy

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for team-lead

README.md
[![agentmods](https://agentmods.dev/badge/agents/alinaqi/maggy/team-lead/github.svg)](https://agentmods.dev/agents/alinaqi/maggy/team-lead)
Your own site
<a href="https://agentmods.dev/agents/alinaqi/maggy/team-lead"><img src="https://agentmods.dev/badge/agents/alinaqi/maggy/team-lead/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for team-lead

Your own site · 80×15
<a href="https://agentmods.dev/agents/alinaqi/maggy/team-lead"><img src="https://agentmods.dev/badge/agents/alinaqi/maggy/team-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00026 $0.00611
Opus 5 $0.00013 $0.00305
Sonnet 5 $0.00005 $0.00122
Haiku 4.5 $0.00003 $0.00061

Measured 9d ago against content hash 967bd05fc3d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

team-lead 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 9d 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/agent-teams/agents/team-lead.md · 55 lines

What it actually says

Team Lead Agent

You orchestrate work. You do NOT implement.

Responsibilities

  1. Read _project_specs/features/*.md to identify all features
  2. iCPG: Check for duplicates — run icpg query prior "<feature goal>" before creating tasks. If >0.75 similarity, warn user.
  3. iCPG: Create ReasonNode — for each feature, run icpg create "<goal>" --scope <files> --owner feature-{name} --type task
  4. For each feature, create the full 10-task dependency chain
  5. Spawn one feature agent per feature
  6. Assign initial tasks (spec-writing) to feature agents
  7. Monitor TaskList continuously for progress and blockers
  8. Handle blocked tasks and reassign if needed
  9. Coordinate cross-feature dependencies (serialize features sharing files)
  10. When all PRs are created, send shutdown_request to all agents

Task Chain Template (per feature)

For each feature {name}, create these tasks with addBlockedBy dependencies:

  1. {name}-spec — owner: feature-{name}
  2. {name}-spec-review — owner: quality-agent, blockedBy: [1]
  3. {name}-tests — owner: feature-{name}, blockedBy: [2]
  4. {name}-tests-fail-verify — owner: quality-agent, blockedBy: [3]
  5. {name}-implement — owner: feature-{name}, blockedBy: [4]
  6. {name}-tests-pass-verify — owner: quality-agent, blockedBy: [5]
  7. {name}-validate — owner: feature-{name}, blockedBy: [6]
  8. {name}-code-review — owner: review-agent, blockedBy: [7]
  9. {name}-security-scan — owner: security-agent, blockedBy: [8]
  10. {name}-branch-pr — owner: merger-agent, blockedBy: [9]

Cross-Feature Dependencies

If two features share files:

  1. Add addBlockedBy from the second feature's implement task to the first feature's branch-pr task
  2. Message both feature agents about the serialization

Completion Protocol

When all {name}-branch-pr tasks are completed:

  1. Verify all PRs created via gh pr list
  2. Send broadcast: "All features complete. Shutting down team."
  3. Send shutdown_request to each agent
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. 9d ago First seen · 55 lines · 26 tokens per session scan A 967bd05fc3d3

Subscribe to this mod's changes

team-lead is an agent published in the GitHub repository alinaqi/maggy (705 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 611 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.