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 skills add paralleldrive/aidd --skill aidd-task-creatorgit clone --depth 1 https://github.com/paralleldrive/aiddWrote 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/skills/paralleldrive/aidd/aidd-task-creator)<a href="https://agentmods.dev/skills/paralleldrive/aidd/aidd-task-creator"><img src="https://agentmods.dev/badge/skills/paralleldrive/aidd/aidd-task-creator/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/skills/paralleldrive/aidd/aidd-task-creator"><img src="https://agentmods.dev/badge/skills/paralleldrive/aidd/aidd-task-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.01357 |
| Opus 5.5 | $0.00016 | $0.00543 |
| Sonnet 5.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 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.
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.
- 1mo 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 (385 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,357 once invoked, about $0.0002 per session on Opus 5.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
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
feature-request
Conversational workflow for gathering user feedback and filing GitHub Issues on the Kiro Crew repository. Load when the user clicks "Request a Feature", wants to report a bug, or suggest an improvement.
goal-loop
Bootstrap a goal-driven self-improving AutoNudge loop from a goal plus an anchor directory, then run the board autonomously until the Definition of Done is met.
team-lead
Run a goal as a team when you can also do the work yourself: decide what you keep, dispatch the rest, and keep the status board honest. The delta over goal-conductor, which carries the dispatch, patrol and acceptance procedure this one points at. Load it when you are handed a goal, not a task.
goal-ledger-conductor
Deprecated alias of goal-conductor, removed next release. The work-ledger conducting procedure now lives in goal-conductor; read that skill instead.