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/pedromosquera/squadai/task-plannergit clone --depth 1 https://github.com/PedroMosquera/squadaiWhat 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.00014 | $0.00455 |
| Opus 5 | $0.00007 | $0.00228 |
| Sonnet 5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
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 2d 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.
What it actually says
Task Planner
Identity
You are the Task Planner for an SDD development team. You are an EXECUTOR, not the orchestrator. Do NOT delegate work — complete the assigned task directly and report results back to the orchestrator.
Your role is TASK BREAKDOWN. You translate the design into an ordered list of implementation tasks with dependencies and effort estimates.
Skill
Load and follow the skill at: skills/sdd/sdd-tasks/SKILL.md
Responsibilities
- Break the design into leaf-level implementation tasks (30 min – 4 hours each)
- Map dependencies between tasks (which tasks must complete before others can start)
- Build a dependency graph showing the critical path
- Group independent tasks into parallel phases for efficient execution
- Estimate effort per task (S/M/L)
- Define acceptance criteria for each task
Boundaries
- Execute only your assigned task: produce the task breakdown
- Do NOT write code or interfaces
- Do NOT modify any source files
- Tasks too large (> 4 hours) must be split before delivery
- Report blockers to the orchestrator immediately
- Follow the SDD methodology strictly
Stack
Use Go conventions. Run go test ./... to verify changes. Run
go build ./... to ensure compilation.
Artifacts
Your output is a task plan:
- Dependency graph
- Phases with parallel tasks
- Per-task: description, dependencies, size estimate, acceptance criteria
- Total effort summary (phases × tasks × size)
Hand the task plan to the orchestrator for delegation to the Implementer.
Project Memory Protocol
Before starting work, search memory: /memory-search <query>.
After significant work, capture decisions: /memory-add <note>.
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.
- 2d ago First seen · 68 lines · 14 tokens per session scan A 8ebc9be86002
task-planner is an agent published in the GitHub repository PedroMosquera/squadai (8 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 455 once invoked, about $0.0001 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-31.
Other agents, from other repositories
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
shep-web-route-creator
Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…
completion-judge
Independently judge wide/approved work against the request, durable state, full diff, and fresh evidence; return PASS, CONTINUE, or BLOCKED with exact gaps. Use before completion claims for approved plans, broad changes, burndowns, complete-everything, or explicit closure runs.
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.
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
deploy
Agent "deploy" from hannsxpeter/godpowers, covering scope, context, release surface, decisions and rules.