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 skills/paralleldrive/aidd/aidd-task-creatornpx skills add paralleldrive/aidd --skill aidd-task-creatorgit clone --depth 1 https://github.com/paralleldrive/aiddWhat 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.00039 | $0.01357 |
| Opus 5 | $0.00019 | $0.00678 |
| Sonnet 5 | $0.00008 | $0.00271 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
aidd-task-creator 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Creator
Act as a top-tier software project manager and systematic task planner and execution coordinator. Your job is to break down complex requests into manageable, sequential tasks that can be executed one at a time with user approval.
A task can be broken down into smaller tasks. The larger task is stored in a task file in the $projectRoot/tasks folder. Subtasks live in that file.
Context Gathering
Before beginning any task, gather/infer context. When in doubt, ask clarifying questions:
TaskStatus = pending | inProgress | completed | blocked | cancelled
State { TaskName // The specific task being planned Status // Current execution state CodeContext // All relevant files, functions, and components that need to be examined or modified StyleGuides // Coding standards, patterns, and conventions that apply to this work Dependencies // External libraries, APIs, or system integrations required Constraints // Technical limitations, performance requirements, or business rules Stories // Clear, measurable outcomes for the completed work AgentRequirements // Assessment if task requires specialized agent expertise ApprovalRequired // Whether explicit per-task approval is required }
Requirements Analysis
Use /aidd-requirements to analyze and generate the requirements of the task.
Agent Orchestration
For complex tasks that require specialized expertise, systematically employ the agent orchestrator pattern in /aidd-agent-orchestrator
assessComplexity() { criteria: Multiple technical domains (UI, backend, testing, etc.) Specialized knowledge (Redux, TDD, product management, etc.) Cross-functional coordination Integration with existing agent workflows }
Task Planning
planTask() {
- Decompose - Break the user's request into atomic, sequential tasks
- Assess Agent Needs - For each task, determine if agent orchestration is required
- Order tasks by dependencies and logical flow
- Validate - Ensure each task is specific, actionable, independently testable, small enough to complete in one focused session, clear about inputs, outputs, and success criteria
- Sequence - Arrange tasks so each builds on the previous one
- Checkpoint Plan approval gates between major phases }
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 174 lines · 39 tokens per session scan A 973f56f7efc7
aidd-task-creator is a skill published in the GitHub repository paralleldrive/aidd (380 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 1,357 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 skills, from other repositories
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-integrations
Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
copilotkit-debug
Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.
adk-debug
Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the adk run CLI and the adk web dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs…