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/niels-emmer/myaceWrote 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/commands/niels-emmer/myace/sdd-tasks)<a href="https://agentmods.dev/commands/niels-emmer/myace/sdd-tasks"><img src="https://agentmods.dev/badge/commands/niels-emmer/myace/sdd-tasks/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/commands/niels-emmer/myace/sdd-tasks"><img src="https://agentmods.dev/badge/commands/niels-emmer/myace/sdd-tasks.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.00032 | $0.00413 |
| Opus 5 | $0.00016 | $0.00206 |
| Sonnet 5 | $0.00006 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
sdd-tasks 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 5d 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
- Read
docs/specs/<slug>/spec.mdanddocs/specs/<slug>/plan.md. - Group tasks by independently-shippable increment — usually one per user story from the spec — rather than by technical layer, so each group is a coherent, demoable slice rather than "all the backend work" followed by "all the frontend work."
- Break each increment into concrete, checkable steps small enough to verify on their own (a migration, an endpoint, a test for a specific edge case) — not vague phases. This mirrors the base
plancommand's step-sizing rule; apply it per-increment here. - Mark tasks that can run in parallel (no shared file, no dependency on another unfinished task) so
sdd-implement— or a human — knows what can be batched. - Verify coverage both directions: every functional requirement and edge case in the spec maps to at least one task, and every task traces back to a requirement in the spec or a supporting need from the plan (data model setup, a new dependency). A task with no requirement behind it is scope creep; a requirement with no task is a gap that will surface as a missed feature later.
- Write the ordered, grouped list to
docs/specs/<slug>/tasks.md. - Recommend running
sdd-analyzebeforesdd-implementif the spec or plan went through more than one round of changes — the more a design shifts, the more likely spec/plan/tasks have quietly drifted out of sync with each other.
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.
- 5d ago First seen · 14 lines · 32 tokens per session scan A 30a85fb1bcf3
sdd-tasks is a command published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 413 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-09-03.
Other commands, from other repositories
address
Address the pressure-test review for a plan.
distill
Distill important session insights into doc/loom/knowledge.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.