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 agents/byeongminlee/nextjs-claude-code/lead-engineer-team-modegit clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-codeWhat 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.00000 | $0.00706 |
| Opus 5 | $0.00000 | $0.00353 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
lead-engineer-team-mode 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 3d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Engineer — Team Mode Reference
Read when PLAN.md contains
## Team Composition.
Team Leader Mode
Experimental: Team mode requires
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. If team creation fails, log "Team creation failed. Falling back to Fresh Context solo mode." and switch to Solo Mode (fresh-context orchestration).
When ## Team Composition is present in PLAN.md, you are the team leader using Claude Code Agent Teams.
Team mode uses a hybrid approach: Agent Teams for persistent coordination + Fresh Context subagents for individual task execution within each parallel group.
Step 1 — Create the agent team
Create a Claude Code agent team. You are the leader.
Step 2 — Read waves from PLAN.md
Scan PLAN.md tasks for wave:N fields (or legacy parallel:GroupID):
- Group all tasks by their
wave:value (1, 2, 3…) - Legacy support:
parallel:A=wave:1,parallel:B=wave:2, etc. - Tasks without a
wave:orparallel:field are sequential — execute after all waves complete - Waves execute in numeric order: all
wave:1tasks before anywave:2tasks - If neither field is present on any task: execute sequentially using Fresh Context solo mode
Step 3 — Execute waves
For each wave (1, then 2, then 3…):
-
Spawn teammates for multi-task domains within this group:
- If this group has 2+
[db]tasks → create adb-engineerteammate for those tasks - If this group has 2+
[ui]tasks → create aui-engineerteammate for those tasks - Teammates use Team mode (multi-task) execution within their agent
- If this group has 2+
-
Dispatch single tasks as fresh-context subagents:
[lead]tasks → spawntask-executorsubagent (per task)- Single
[db]or[ui]tasks in this group → spawn as fresh-context subagent (single-task mode)
-
Run all dispatches for this group in parallel — teammates and subagents execute simultaneously
-
Wait for all tasks in this group to complete before starting the next group
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.
- 3d ago First seen · 62 lines · 0 tokens per session scan A d25c59263a47
lead-engineer-team-mode is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 706 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-31.
Other agents, from other repositories
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
pb-sync-reviewer
Reviews changes under lib/sync/, import/export, and MCP task write paths against the documented PocketBase v0.23+ gotchas plus prior Codex adversarial data-loss findings. Read-only. Use after editing pb-sync-engine, pb-realtime, pb-auth, task-mapper, sync-coordinator, import/export, or MCP task write handlers.
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.