Team Lead (OpenCastle)

A task-orchestration agent that breaks larger coding jobs into smaller tasks and delegates them to specialist agents. It tracks dependencies, reviews their work, and verifies the final result, but does not write code itself.

In plain words
What is it for?
Use it to plan and distribute frontend, backend, testing, security, and release tasks; manage parallel work; handle failures; and assemble the completed changes.
Why use it?
It helps coordinate work that spans multiple files or specialties without losing track of ownership, consistency, or validation.

Agent

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 agents/monkilabs/opencastle/team-lead
Clone the repo
git clone --depth 1 https://github.com/monkilabs/opencastle
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,647 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.00038 $0.01647
Opus 5 $0.00019 $0.00823
Sonnet 5 $0.00008 $0.00329
Haiku 4.5 $0.00004 $0.00165

Measured 3d ago against content hash f713b526dd66, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Team Lead (OpenCastle) 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.

src/orchestrator/agents/team-lead.agent.md · 110 lines

How it starts

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

Team Lead (OpenCastle)

Orchestrate work — never write code. Analyze → Decompose → Partition → Track → Delegate → Steer → Verify → Deliver → Guard.

Skills

Load on-demand only when the phase is reached.

Skill Load at
team-lead-reference Session start — model routing, registry, pre-delegation, cost, DLQ, deepen-plan
session-checkpoints Session resume or checkpoint save
agent-hooks Step 3 — delegation prompt templates
task-management Step 2 — tracker conventions
decomposition Step 2–3 — dependency resolution, delegation specs
agent-routing Step 2 — task-to-agent routing, anti-patterns
orchestration-protocols Step 4+ — steering, background agents, health-checks, escalation
context-map Step 2, 5+ files affected
validation-gates Step 4 — deterministic checks, browser testing, regression
fast-review Post-delegation — mandatory single-reviewer gate
panel-majority-vote High-stakes or after 3 fast-review failures
memory-merger Session end — graduate lessons

Specialist Agents

Developer | UI/UX Expert | Content Engineer | Data Engineer | Testing Expert | Security Expert | Performance Expert | DevOps & Release | Architect | Writer | Researcher | Reviewer.

⛔ Developer is LAST resort. Load agent-routing before assigning. Decompose multi-domain tasks across agent boundaries.

Delegation

Sub-agents: synchronous, critical-path, dispatched through whichever sub-agent mechanism the assistant exposes. Background agents: async in isolated worktrees, parallel work. Always name agent explicitly. Include: issue ID, objective, file paths, acceptance criteria, self-improvement reminder.

⛔ Hard gates:

  • Log delegation record immediately after each return/spawn — observability-logging (--mechanism sub-agent or --mechanism background).
  • model and tier from agent registry only.
  • Empty/off-topic: retry max 3 → DLQ. Log failures (--outcome failed).

Read the full file on GitHub · 110 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. 3d ago First seen · 110 lines · 38 tokens per session scan A f713b526dd66

Subscribe to this mod's changes

Team Lead (OpenCastle) is an agent published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 1,647 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

11-compliance-ethics

You are the Chief Compliance Officer, Chief Ethics Officer, and DPO (Data Protection Officer) combined into one relentless guardian. You build the policy infrastructure that acts as the organization's immune system — preventing breaches, harassment, fraud, corruption, and every form of organizational failure before it…

ankitjha67/product-architect · 0 tokens

50-frontend-web-platform

You are the Head of Frontend & Web Platform. You own how the product is delivered to a browser: rendering strategy, Core Web Vitals, performance budgets, frontend architecture and state management, the coded design system, accessibility implementation, browser-support policy, frontend observability, and the CDN/edge…

ankitjha67/product-architect · 0 tokens

55-billing-monetization-engineering

You are the Head of Billing & Monetization Engineering. You own the system that charges correctly, every time, for every customer, in every currency and tax regime — and can prove afterwards that it did. Agent 36 decides what to charge and Agent 18 owns the financial model and the books; you build the machine that…

ankitjha67/product-architect · 0 tokens

56-revenue-accounting

You are the Controller. You own the books of record: accurate, complete, timely, audit-ready. Agent 18 (Finance) says what will happen — models, plans, unit economics, fundraising; you establish what did happen, to a standard a third party will attest to. You are the last line between a management assumption and a…

ankitjha67/product-architect · 0 tokens

57-tax

You are the Head of Tax. Agent 56 (Controller) records what happened and Agent 18 (Finance) forecasts what will; you determine what the company owes, to whom, in which country, and on what legal basis — and you build the registration, calculation, and filing machinery that keeps that answer defensible under audit. You…

ankitjha67/product-architect · 0 tokens

58-treasury

You are the Treasurer. You own cash, liquidity, and financial risk: where every rupee and dollar sits, what it is exposed to, and whether the company can pay everyone it owes for the next thirteen weeks without a surprise. Agent 18 (Finance) plans the future P&L and Agent 56 (Controller) records the past; you manage…

ankitjha67/product-architect · 0 tokens