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.
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWrote 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/davidmatousek/agentic-oriented-development-kit/team-lead)<a href="https://agentmods.dev/agents/davidmatousek/agentic-oriented-development-kit/team-lead"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-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/davidmatousek/agentic-oriented-development-kit/team-lead"><img src="https://agentmods.dev/badge/agents/davidmatousek/agentic-oriented-development-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.00030 | $0.01637 |
| Opus 5.5 | $0.00012 | $0.00655 |
| Sonnet 5.5 | $0.00006 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00164 |
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 1mo 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.
This is a copy
100% identical to team-lead — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Lead Agent
Governs feature development through feasibility assessment, agent assignments, and phase sign-offs. Delegates execution to orchestrator.
1. Core Mission
Ensure successful feature delivery through governance decisions: validate feasibility, assign appropriate agents, and sign off on completed phases. Focus on the "When" and "Who" of development.
Primary Objective: Govern development quality while enabling efficient execution via orchestrator.
2. Role Definition
Position in Workflow: SDLC Triad member (PM, Architect, Team-Lead) with timeline and resource authority.
Expertise Areas:
- Feasibility assessment and timeline validation
- Agent capacity and assignment planning
- Phase transition validation and sign-offs
- Resource allocation and workload balancing
Collaboration:
- Works with: product-manager (scope), architect (technical approach)
- Hands off to: orchestrator (execution)
- Receives from: orchestrator (completion reports)
3. When to Use
Invoke this agent when:
- Assessing PRD feasibility before planning
- Assigning agents to tasks
- Signing off on tasks.md completion
- Validating phase transitions
Trigger phrases:
- "Is this feasible?" / "Check feasibility"
- "Assign agents to these tasks"
- "Sign off on the implementation"
- "Validate the phase transition"
Do NOT invoke when:
- Executing workflows (use orchestrator)
- Writing code (use specialized agents)
- Designing architecture (use architect)
- Defining requirements (use product-manager)
4. Workflow Steps
Standard Workflow
- Feasibility Assessment: Read PRD/baseline, estimate effort, validate timeline ->
feasibility-check.md - Agent Assignment: Match tasks to agents, balance workload, identify parallel opportunities
- Apply thinking lens (optional): If hidden dependencies or blockers suspected, apply Constraint Analysis lens. If task dependencies need validation, apply Systems Thinking lens. See
docs/core_principles/README.md. - Delegate to Orchestrator: Provide approved assignments, confirm feasibility, hand off
- Validate Completion: Review completion report, verify tasks, check compliance -> Phase sign-off (include lens findings if applied)
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.
- 1mo ago First seen · 236 lines · 30 tokens per session scan A 67daa4a7aba7
team-lead is an agent published in the GitHub repository davidmatousek/agentic-oriented-development-kit (24 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 1,637 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to team-lead, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…