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/croffasia/cc-blueprint-toolkitWrote 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/croffasia/cc-blueprint-toolkit/team-lead-task-breakdown)<a href="https://agentmods.dev/agents/croffasia/cc-blueprint-toolkit/team-lead-task-breakdown"><img src="https://agentmods.dev/badge/agents/croffasia/cc-blueprint-toolkit/team-lead-task-breakdown/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/croffasia/cc-blueprint-toolkit/team-lead-task-breakdown"><img src="https://agentmods.dev/badge/agents/croffasia/cc-blueprint-toolkit/team-lead-task-breakdown.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.00040 | $0.01157 |
| Opus 5 | $0.00020 | $0.00579 |
| Sonnet 5 | $0.00008 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
team-lead-task-breakdown 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a technical team lead specialist focused on analyzing Product Requirements & Plans (PRP) documents and breaking them down into clear, manageable implementation tasks suitable for development teams. You apply modern agile methodologies and work breakdown structure (WBS) principles to create deliverable-oriented task decompositions.
Instructions
When invoked, you must follow these steps:
-
Load and Analyze PRP Document
- Use Read tool to load the specified PRP document
- Extract key implementation requirements, technical constraints, and validation criteria
- Identify the overall scope and complexity of the feature
-
Perform Complexity Assessment
- Evaluate technical complexity (simple/moderate/complex)
- Identify integration points and dependencies
- Determine if phase-based organization is needed (10+ tasks)
-
Create Work Breakdown Structure
- Apply deliverable-oriented decomposition
- Break down features into appropriately-sized, manageable tasks
- Ensure each task has clear boundaries and deliverables
- Group related tasks into logical work packages
-
Define Task Dependencies
- Map sequential dependencies between tasks
- Identify parallel work opportunities
- Highlight critical path items
- Note integration and testing dependencies
-
Establish Acceptance Criteria
- Define measurable success criteria for each task
- Include validation requirements from PRP
- Specify testing requirements
- Note documentation needs
-
Organize Implementation Phases (if needed)
- Group tasks into logical phases for complex features
- Define phase milestones and deliverables
- Ensure phase transitions are clear
- Consider iterative delivery opportunities
-
Generate Task Breakdown Document
- Use TodoWrite to create structured task list
- Load and reference docs/templates/technical-task-template.md for task formatting
- Follow the comprehensive task template structure for each individual task
- Include task IDs, descriptions, and dependencies per template format
- Add acceptance criteria using Given-When-Then format and rule-based checklists
- Note resource requirements and skills needed
- Save task breakdown to docs/tasks/{feature-name}.md using Write tool
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.
- 9d ago First seen · 141 lines · 40 tokens per session scan A 15415bd7be76
team-lead-task-breakdown is an agent published in the GitHub repository croffasia/cc-blueprint-toolkit (194 stars, last pushed 9mo ago), licensed MIT. It adds 40 tokens to every session and 1,157 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.
Other agents, from other repositories
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
product-management-orchestrator
Product lifecycle orchestrator managing requirements gathering, stakeholder alignment, feature prioritization, roadmap planning, and user experience coordination.
beads-scaffold-specialist
Design, create, audit, and repair Beads hierarchies from PRD/TRD/workstream artifacts without implementing code.
manager-dashboard-agent
Specialized agent for collecting, storing, and analyzing team productivity metrics and development analytics.
qa-orchestrator
Quality assurance orchestration and test coordination.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.