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-specify)<a href="https://agentmods.dev/commands/niels-emmer/myace/sdd-specify"><img src="https://agentmods.dev/badge/commands/niels-emmer/myace/sdd-specify/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-specify"><img src="https://agentmods.dev/badge/commands/niels-emmer/myace/sdd-specify.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.00030 | $0.00438 |
| Opus 5 | $0.00015 | $0.00219 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
sdd-specify 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
- Restate the request as a short slug (
kebab-case, e.g.sso-login) and createdocs/specs/<slug>/spec.md. - Write the spec in terms a non-technical stakeholder could review: user stories ("As a ..., I want ..., so that ..."), functional requirements, and explicit out-of-scope items. Say nothing about frameworks, data models, or file structure here — that's
sdd-plan's job, not this one. - Write acceptance criteria as testable statements, not adjectives — "the export completes within 30s for a 10k-row account" is testable; "the export is fast" is not.
- Where the request is genuinely ambiguous, don't guess silently and don't stall on every open question — make the reasonable, industry-standard assumption and note it, and only mark the ones that actually change scope, data ownership, or security posture as
[NEEDS CLARIFICATION: ...]. Cap it at the handful that matter; a spec with twenty clarification markers wasn't specified, it was punted. - List edge cases explicitly (empty states, concurrent access, partial failure) — a spec that only describes the happy path will produce a plan and task list that only covers the happy path.
- Read the project constitution (
docs/constitution.md, ifsdd-constitutionhas been run) and flag anything in the request that appears to conflict with a listed principle, rather than silently specifying around it. - Report the spec's location and a one-line summary of what's still marked
[NEEDS CLARIFICATION]. If there are any, the next step issdd-clarify, notsdd-plan.
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 · 30 tokens per session scan A 90334393f522
sdd-specify is a command published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 438 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.