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-auditgit 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-audit)<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-reverse-audit"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-reverse-audit.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.00053 | $0.00827 |
| Opus 5 | $0.00026 | $0.00413 |
| Sonnet 5 | $0.00011 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
sdd-reverse-audit 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-reverse-audit {LegacyProject} [--force-enrichment-on Entity.field] [--json]
Rôle
Lancer la Phase 2 : audit architecture / anti-patterns / dépendances EOL + enrichissement DB schema. Optionnel : Phase 3 ne dépend PAS de Phase 2 (cf. design doc §4.2).
Args
| Arg | Type | Description |
|---|---|---|
{LegacyProject} |
string requis | Sous-dossier de workspace/old/ (Phase 1 préalable obligatoire) |
--force-enrichment-on Entity.field |
flag répétable | ADV-12 : permet à enrichment.json d'override le base sur ce field (en cas de conflit type) |
--json |
flag | Émet rapport audit en JSON |
Pré-conditions
workspace/old/{LegacyProject}/.sys/inventory.jsondoit exister (Phase 1)workspace/old/{LegacyProject}/.sys/db-schema.jsondoit exister (Phase 1)
Sinon → STOP + ERROR [REVERSE_NO_SOURCE] + suggérer /sdd-reverse-inventory {LegacyProject} d'abord.
Actions
- Script déterministe d'abord :
Produitpython .sdd/python/sdd_reverse_scripts/reverse_audit.py \ --project workspace/old/{LegacyProject} \ [--force-enrichment-on ...]deps-graph.json+ skeletondb-schema.enrichment.json+db-schema.merged.json. - Spawn unique
Agent(reverse-tech-auditor)qui enrichittech-audit.md(FR) + remplitdb-schema.enrichment.jsonavec relations/fields/indexes déduits. - Re-merge : le merge_db_schema.py est re-déclenché par l'agent post-enrichment (idempotent).
- Émission ligne chat finale
[REVERSE] Audit complet. {anti-patterns} anti-patterns, {eol} EOL deps. (28%)
Sortie
workspace/old/{LegacyProject}/.sys/
├── tech-audit.md (FR narratif, par agent)
├── deps-graph.json (script, design doc §5.4)
├── db-schema.enrichment.json (enrichi par agent, ADV-3)
└── db-schema.merged.json (union déterministe via merge_db_schema)
Skippable
Phase 2 est purement informational. Phase 3 fonctionne sans elle (lit db-schema.json base si db-schema.merged.json absent). Skip avec /sdd-reverse-full --skip-audit (V2).
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 · 64 lines · 53 tokens per session scan A 91edd934d5af
sdd-reverse-audit is a command published in the GitHub repository zekiriabd/SDD-Pro (191 stars, last pushed 2d ago), licensed Apache-2.0. It adds 53 tokens to every session and 827 once invoked, about $0.0003 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.