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-implement)<a href="https://agentmods.dev/commands/niels-emmer/myace/sdd-implement"><img src="https://agentmods.dev/badge/commands/niels-emmer/myace/sdd-implement/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-implement"><img src="https://agentmods.dev/badge/commands/niels-emmer/myace/sdd-implement.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.00028 | $0.00429 |
| Opus 5.5 | $0.00011 | $0.00172 |
| Sonnet 5.5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
sdd-implement 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.
What it actually says
- Read
docs/specs/<slug>/tasks.mdand the underlyingspec.md/plan.md. Ifsdd-analyzehasn't been run and the spec or plan changed aftersdd-taskswas generated, run it first rather than implementing against a possibly-stale task list. - Work through tasks in the order and grouping
sdd-tasksproduced. Within a group, tasks marked parallel-safe may be done in any order; tasks with a stated dependency must wait for it. - For each task, write the test that would fail without the change first, then implement until it passes — the same discipline as the
test-patternsskill, applied task-by-task rather than once at the end. - Mark each task complete in
tasks.mdas it finishes, so progress is visible and a resumed session picks up where the last one left off instead of re-deriving what's already done. - On a failure in a non-parallel task, stop and surface it rather than skipping ahead to unblocked-looking later tasks — a later task may implicitly depend on the failed one in a way
sdd-tasksdidn't capture explicitly. - Once every task is complete, hand off to the base
verifycommand (if composed) for the full pre-merge check — this command's job is to execute the task list correctly, not to duplicate the project's whole test/lint/security/docs gate. - Report which tasks completed, which were skipped and why, and the spec's acceptance criteria status — don't report the feature done until every acceptance criterion in
spec.mdis demonstrably met, not just every task checked off.
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 · 14 lines · 28 tokens per session scan A a310a491bd21
sdd-implement is a command published in the GitHub repository niels-emmer/myace (1 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 429 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
run
A command for implementing written software requirements using domain-driven design (DDD) and test-driven development (TDD). DDD structures code around the business domain, while TDD starts with tests before implementation.
test
A test-driven development workflow, or TDD, where tests describing the expected behavior are written before the implementation. For bugs, it first adds a test that reproduces the failure.
debug
Systematic root-cause investigation, then fix with TDD — never proposes a fix before finding the cause; resumable diagnosis + regression test in .orc/ state. Workspace-aware. For a quick one-off look without session state, prefer the bundled /debug.
tdd
Guide a Test-Driven Development workflow for the current task.
9_gofer_tests
Generate comprehensive test suites from four testing perspectives for a target component.
flutter-test
Generate Vitest/Flutter tests for Dart code following TDD patterns from the magic-framework skill.