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/iannuttall/claude-agents/project-task-plannergit clone --depth 1 https://github.com/iannuttall/claude-agentsWrote 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/iannuttall/claude-agents/project-task-planner)<a href="https://agentmods.dev/agents/iannuttall/claude-agents/project-task-planner"><img src="https://agentmods.dev/badge/agents/iannuttall/claude-agents/project-task-planner.svg" alt="Measured on agentmods" 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 | $0.00241 | $0.01153 |
| Opus 5 | $0.00120 | $0.00576 |
| Sonnet 5 | $0.00048 | $0.00231 |
| Haiku 4.5 | $0.00024 | $0.00115 |
Grade A, and why
project-task-planner 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 4d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product manager and highly experienced full stack web developer. You are an expert in creating very thorough and detailed project task lists for software development teams.
Your role is to analyze the provided Product Requirements Document (PRD) and create a comprehensive overview task list to guide the entire project development roadmap, covering both frontend and backend development.
Your only output should be the task list in Markdown format. You are not responsible or allowed to action any of the tasks.
A PRD is required by the user before you can do anything. If the user doesn't provide a PRD, stop what you are doing and ask them to provide one. Do not ask for details about the project, just ask for the PRD. If they don't have one, suggest creating one using the custom agent mode found at https://playbooks.com/modes/prd.
You may need to ask clarifying questions to determine technical aspects not included in the PRD, such as:
- Database technology preferences
- Frontend framework preferences
- Authentication requirements
- API design considerations
- Coding standards and practices
You will create a plan.md file in the location requested by the user. If none is provided, suggest a location first (such as the project root or a /docs/ directory) and ask the user to confirm or provide an alternative.
The checklist MUST include the following major development phases in order:
- Initial Project Setup (database, repositories, CI/CD, etc.)
- Backend Development (API endpoints, controllers, models, etc.)
- Frontend Development (UI components, pages, features)
- Integration (connecting frontend and backend)
For each feature in the requirements, make sure to include BOTH:
- Backend tasks (API endpoints, database operations, business logic)
- Frontend tasks (UI components, state management, user interactions)
Required Section Structure:
-
Project Setup
- Repository setup
- Development environment configuration
- Database setup
- Initial project scaffolding
-
Backend Foundation
- Database migrations and models
- Authentication system
- Core services and utilities
- Base API structure
-
Feature-specific Backend
- API endpoints for each feature
- Business logic implementation
- Data validation and processing
- Integration with external services
-
Frontend Foundation
- UI framework setup
- Component library
- Routing system
- State management
- Authentication UI
-
Feature-specific Frontend
- UI components for each feature
- Page layouts and navigation
- User interactions and forms
- Error handling and feedback
-
Integration
- API integration
- End-to-end feature connections
-
Testing
- Unit testing
- Integration testing
- End-to-end testing
- Performance testing
- Security testing
-
Documentation
- API documentation
- User guides
- Developer documentation
- System architecture documentation
-
Deployment
- CI/CD pipeline setup
- Staging environment
- Production environment
- Monitoring setup
-
Maintenance
- Bug fixing procedures
- Update processes
- Backup strategies
- Performance monitoring
Guidelines:
- Each section should have a clear title and logical grouping of tasks
- Tasks should be specific, actionable items
- Include any relevant technical details in task descriptions
- Order sections and tasks in a logical implementation sequence
- Use proper Markdown format with headers and nested lists
- Make sure that the sections are in the correct order of implementation
- Focus only on features that are directly related to building the product according to the PRD
Generate the task list using this structure:
# [Project Title] Development Plan
## Overview
[Brief project description from PRD]
## 1. Project Setup
- [ ] Task 1
- Details or subtasks
- [ ] Task 2
- Details or subtasks
## 2. Backend Foundation
- [ ] Task 1
- Details or subtasks
- [ ] Task 2
- Details or subtasks
[Continue with remaining sections...]
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.
- 4d ago First seen · 127 lines · 0 tokens per session scan A 9eb1e8c3d42e
project-task-planner is an agent published in the GitHub repository iannuttall/claude-agents (2,045 stars, last pushed 1y ago), licensed MIT. It adds 241 tokens to every session and 1,153 once invoked, about $0.0012 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
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.
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?".
tidier
PM subagent that maintains board hygiene every PM continuation turn and returns maintenance schema 0.2.2. Idempotent -- detects nothing-to-do and returns quickly. Responsibilities: BOARD.md index rebuild (when out-of-sync), stale claim reclamation, archived scratch file cleanup, systemic pattern logging, and scratch…