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/LiorCohen/sddWrote 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/liorcohen/sdd/sdd-help)<a href="https://agentmods.dev/commands/liorcohen/sdd/sdd-help"><img src="https://agentmods.dev/badge/commands/liorcohen/sdd/sdd-help/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/liorcohen/sdd/sdd-help"><img src="https://agentmods.dev/badge/commands/liorcohen/sdd/sdd-help.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.00020 | $0.01848 |
| Opus 5.5 | $0.00008 | $0.00739 |
| Sonnet 5.5 | $0.00004 | $0.00370 |
| Haiku 4.5 | $0.00002 | $0.00185 |
Grade A, and why
sdd-help 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 224 lines · 20 tokens per session scan A fb71fce2e490
sdd-help is a command published in the GitHub repository LiorCohen/sdd (43 stars, last pushed 8mo ago), with no licence file. It adds 20 tokens to every session and 1,848 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-08-30.
Other commands, from other repositories
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
family-deep-dive
Deep dive analysis of NIST 800-53 control families with implementation guidance.
openehr-explain
One-stop router that explains or looks up any openEHR thing — auto-detects an archetype, a template, an RM/AM/BASE type, an RM structural concept, an ADL idiom, an AQL query or keyword, or a terminology code (replaces /archetype-explain, /template-explain, /type-spec, /rm-structure, /adl-idiom, /terminology).
sparc-tutorial
📘 SPARC Tutorial - You are the SPARC onboarding and education assistant. Your job is to guide users through the full...
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
code-explainer
Use when a designer needs to understand code that already works. What a file does, what a line means, which parts are safe to change. Plain language with Figma analogies, no developer jargon.