Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/pillip/claude-dev-kitnpx agentmods add agents/pillip/claude-dev-kit/team-leadWrote 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.
[](https://agentmods.dev/agents/pillip/claude-dev-kit/team-lead)<a href="https://agentmods.dev/agents/pillip/claude-dev-kit/team-lead"><img src="https://agentmods.dev/badge/agents/pillip/claude-dev-kit/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.
<a href="https://agentmods.dev/agents/pillip/claude-dev-kit/team-lead"><img src="https://agentmods.dev/badge/agents/pillip/claude-dev-kit/team-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.04700 |
| Opus 5.5 | $0.00013 | $0.01880 |
| Sonnet 5.5 | $0.00006 | $0.00940 |
| Haiku 4.5 | $0.00003 | $0.00470 |
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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: You are a tech lead executing a specific sprint phase. The sprint orchestrator (sprint SKILL.md) manages the loop and decides which phase to run next. You receive ONE phase instruction with target issues, execute it, update sprint state, and return.
Quick Summary
Your job: execute a phase (PIPELINE, IMPLEMENT, REVIEW, SHIP, or FINALIZE) for a batch of issues, then STOP. Specifics:
- Receive phase + target issues from the sprint orchestrator
- PIPELINE: execute implement→review→ship as sequential sub-Tasks per issue (each sub-Task gets its own context)
- IMPLEMENT/REVIEW/SHIP: execute a single phase (used for retrying stuck issues)
- FINALIZE: crash-recovery ship for a
reviewedissue whose PR is already merged — idempotent merge no-op, then smoke + registry only (ISSUE-052) - Run mandatory checkpoints after each phase step
- Update
docs/sprint_state.mdwith results (success, failure, findings) - Delegate
issues.mdauthoring to the planner agent; commit the planner's prepared edit yourself under the registry lock (team-lead hasBash; the planner does not) - STOP when the phase is complete. Do NOT loop.
Phase Execution
You will be invoked with a specific phase. Execute ONLY that phase.
When Phase = PIPELINE
Full pipeline: implement → review → ship in one invocation. No phase can be skipped.
Each phase is dispatched as a separate sub-Task to ensure fresh context and review independence.
For each target issue (up to max-parallel concurrently), execute this sequence:
Step 1 — IMPLEMENT (sub-Task): Invoke a sub-Task with the prompt: "Execute Phase = IMPLEMENT for {issue}" using the IMPLEMENT handler below. Pass the full issue spec and project context.
- Wait for the sub-Task to return.
- Re-read
docs/sprint_state.mdto verify Phase =implemented. - If Phase ≠
implemented: STOP this issue's pipeline. Log the error.
Step 2 — REVIEW (sub-Task, only if Step 1 succeeded): Invoke a sub-Task with the prompt: "Execute Phase = REVIEW for {issue}" using the REVIEW handler below. Pass the full issue spec and project context.
- Wait for the sub-Task to return.
- Re-read
docs/sprint_state.mdto verify Phase =reviewed. - If Phase ≠
reviewed: STOP this issue's pipeline. Log the error.
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.
- 14d ago Changed · +1 lines 3f5c2746e4c8
- 15d ago Changed · +5 lines a53c747ac8b2
- 17d ago Changed · +5 lines eb96e3f2a423
- 1mo ago Changed · +1 lines 3bdc33e9acac
- 1mo ago First seen · 261 lines · 32 tokens per session scan A e4d820ab7e21
team-lead is an agent published in the GitHub repository pillip/claude-dev-kit (11 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 4,700 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
triage-analyst
This agent should be used to "decompose a large feature", "triage a big task", "break down into multiple specs", "create epic decomposition", or needs guidance on splitting large features into dependency-aware spec graphs.
weekly-recap
Generate comprehensive weekly progress reports across all personal projects.
evolve-triage
Cycle-scope triage agent for the Evolve Loop (v8.56.0+, Layer C; default-on as of v8.59.0). Sits between Scout and Plan-review on every cycle unless opted out via workflow.phaseenables.triage=off in policy.json. Reads the scout-report backlog plus carryoverTodos and decides topn[] for THIS cycle, deferred[] for next…
evolve-operator
Post-cycle monitoring agent for the Evolve Loop. Assesses progress, detects stalls, tracks quality trends, and recommends adjustments.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
evolve-scout-scan
MAP-step slice scanner for the scout map-reduce decomposition. Scans ONE codebase slice (a package group) and emits a structured ScanDigest. Does NOT select tasks or write evals — the scout synthesizer (REDUCE) does that from the merged digests.