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-reverse-featgit 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-reverse-feat)<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-reverse-feat"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-reverse-feat.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.00115 | $0.01124 |
| Opus 5 | $0.00057 | $0.00562 |
| Sonnet 5 | $0.00023 | $0.00225 |
| Haiku 4.5 | $0.00012 | $0.00112 |
Grade A, and why
sdd-reverse-feat 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-reverse-feat {U-N} [--json]
Rôle
Lancer la Phase 3c (barreau du haut) : composer la FEAT métier propre à
partir des User Stories 3b, plomberie démotée, evidence résolue
transitivement. C'est le pont vers /sdd-full (Intent A→B).
us/{n}-{m}-{Name}.md --[3c /sdd-reverse-feat]--> feats/{n}-{FeatName}.md
Remplace l'ex-/sdd-reverse mono-saut (extracteur décommissionné, ADR reverse-spec-ladder).
Args
| Arg | Type | Description |
|---|---|---|
{U-N} |
string requis | Identifiant U-N stable (ex. U-3) |
--json |
flag | Émet le rapport en JSON |
Pré-conditions
(n, FeatName)résolu viainventory.json._featAllocations[{U-N}](3a a tourné). Absent → ERROR[REVERSE_UNIT_NOT_FOUND].- ≥ 1 US
workspace/us/{n}-{m}-{Name}.md(3b a tourné). Aucune → ERROR[REVERSE_UNIT_NOT_FOUND]+ suggérer/sdd-reverse-stories {U-N}. workspace/plans/{n}-{FeatName}.analysis.md(3a — résolution evidence). Absente → ERROR[REVERSE_UNIT_NOT_FOUND]..sdd/python/sdd_reverse/feat.reverse.template.mdprésent (ADV-9). Sinon → ERROR[REVERSE_TEMPLATE_MISSING].
Actions
- Résoudre le projet legacy via
inventory.json._featAllocations. Le nom retenu est{P}— toutes les étapes suivantes l'utilisent, jamais un re-glob. - Routage de tier (déterministe, ADR
governance-reverse-complexity-ladder) — sur le projet{P}résolu en 1 :
→python .sdd/python/sdd_reverse/code_unit_complexity.py \ --project workspace/old/{P} --unit {U-N} --rung 3cbalancedsisimple,deepsicomplex(même classifieur que 3a → la classe est stable sur tout l'escalier ; rubriquedocs/rubrics/reverse-complexity-routing.md). Fail-safe câblé : toute erreur imprimedeepsur stdout + la raison sur stderr, exit 0 — jamais de traceback à la place d'un tier. - Spawn unique
Agent(reverse-feat-composer)avec args ={U-N}ETmodel_tier= le tier routé en 2 (override au spawn, borné partier_floor/tier_ceilingde l'agent — agent inchangé, no-spawn préservé). - L'agent suit STEP 0 à 6 de
.sdd/agents/reverse-feat-composer.md(composition + validate_reverse_feat max 3 + check_feat_completeness). - Émission ligne chat finale
[REVERSE] {U-N} → FEAT {n}-{FeatName} ({modèle}, ...). (PROGRESS%).
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 · 72 lines · 115 tokens per session scan A 116dfaf6a84e
sdd-reverse-feat is a command published in the GitHub repository zekiriabd/SDD-Pro (191 stars, last pushed 2d ago), licensed Apache-2.0. It adds 115 tokens to every session and 1,124 once invoked, about $0.0006 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.