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 agentmods add commands/zekiriabd/sdd-pro/sdd-discover-stackgit clone --depth 1 https://github.com/zekiriabd/SDD-ProWrote 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/zekiriabd/sdd-pro/sdd-discover-stack)<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-discover-stack"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-discover-stack.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.03210 |
| Opus 5 | $0.00011 | $0.01605 |
| Sonnet 5 | $0.00004 | $0.00642 |
| Haiku 4.5 | $0.00002 | $0.00321 |
Grade A, and why
sdd-discover-stack 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 4d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-discover-stack — Détection automatique du stack d'un repo existant
Scanne un repo (brownfield ou nouveau) et produit
workspace/stack/stack.md.candidate avec les stack-ids SDD_Pro
candidats + une ## Project Config pré-remplie. Le Tech Lead arbitre
les ambiguïtés et renomme .candidate → stack.md quand validé.
Usage : /sdd-discover-stack [--scope <path>] [--force]
Garanties non-régression :
- Cette commande ne touche jamais au moteur SDD_Pro (build_loop, API
Gate, phases auditor, file ownership). Elle ne fait que lire des
fichiers manifestes et écrire un
.candidateà côté. - Si
stack.mdexiste déjà → écrit dansstack.md.candidate(jamais d'overwrite direct sauf--force). - Scripts Python déterministes (0 token LLM jusqu'à STEP 5).
STEP 1 — Args
| Arg | Défaut | Sens |
|---|---|---|
--scope <path> |
. |
Répertoire à scanner (relatif au repo root) |
--force |
absent | Autorise overwrite de workspace/stack/stack.md existant |
Si l'arg --scope est absent → scan du repo root.
STEP 2 — Pré-check existence stack.md
STACK_MD = workspace/stack/stack.md
STACK_CANDIDATE = workspace/stack/stack.md.candidate
- Si
STACK_MDexiste ET--forceabsent → cible de sortie =STACK_CANDIDATE - Si
STACK_MDexiste ET--forceprésent → cible de sortie =STACK_MD(overwrite) - Si
STACK_MDabsent → cible de sortie =STACK_MDdirectement
Informer l'utilisateur de la cible choisie :
🔍 /sdd-discover-stack: scanne {scope}, écrira → {target_path}
STEP 3 — Scan déterministe
Invoquer :
python .sdd/python/sdd_scripts/scan_repo.py \
--scope {scope} \
--output workspace/.sys/.audit/scan-report.json \
--quiet
Le script écrit scan-report.json avec :
manifests[]: fichiers détectés (csproj, package.json, etc.) + leur contenu parsélanguages[],frameworks[],ui_indicators[],database_indicators[],auth_indicators[]warnings[]: éventuels[SCAN_PARSE_ERROR]
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.
- 4d ago First seen · 318 lines · 22 tokens per session scan A 6fbd1f298f9f
sdd-discover-stack is a command published in the GitHub repository zekiriabd/SDD-Pro (190 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 3,210 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.