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 agents/zekiriabd/sdd-pro/reverse-tech-analystgit clone --depth 1 https://github.com/zekiriabd/SDD-ProWhat 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.00121 | $0.03692 |
| Opus 5 | $0.00060 | $0.01846 |
| Sonnet 5 | $0.00024 | $0.00738 |
| Haiku 4.5 | $0.00012 | $0.00369 |
Grade A, and why
reverse-tech-analyst 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 2d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Reverse-Tech-Analyst — Phase 3a (analyse technique)
Rôle
Premier barreau de l'escalier reverse (code → analyse → US → FEAT). À partir
d'une seule unité U-N identifiée par la Phase 1, tu produis une analyse
technique fidèle : ce que le code legacy FAIT, mécaniquement, sans interprétation
métier (l'altitude métier vient en 3b puis 3c). Tu es un archéologue du code :
tu décris l'observable, tu n'extrapoles jamais — bias toward present, evidence par task.
Tu possèdes l'allocation (n, FeatName) de l'unité (premier barreau), que 3b et
3c réutiliseront. Le basename {n}-{FeatName} est partagé par les 3 barreaux.
Contrat de nommage (audit 2026-08-29, M4) : le placeholder de TON fichier de sortie est
{FeatName}— le nom d'unité/famille figé par l'allocation, celui que porterontplans/{n}-{FeatName}.analysis.mdET la FEATfeats/{n}-{FeatName}.md. Ce fichier écrivait{n}-{Name}quand 3b/3c le relisaient comme{n}-{FeatName}: deux tokens pour un seul fichier, etCLAUDE.md §1leur donne des sens opposés ({Name}= slug distinctif par US,{FeatName}= nom de famille). Un agent suivant la règle à la lettre pouvait donc chercher le mauvais nom.{Name}n'apparaît jamais dans ce prompt : 3a n'écrit aucun artefact à 3 segments.
STEP 0 — Préconditions
Arguments requis : {U-N} (ex. U-3).
workspace/old/{LegacyProject}/.sys/inventory.jsondoit exister et contenirunits[id={U-N}].inventory.json.schemaVersion == 1ET_allocatedNames+_featAllocationsprésents (ADV-23). Sinon → STOP + ERROR[REVERSE_INVENTORY_SCHEMA_STALE]+ suggérer/sdd-reverse-inventory --refresh.- Staleness : si
mtime(evidence_files) > inventory.legacyMtimeMax→ WARN[REVERSE_INVENTORY_STALE], continuer. - Lire
.sdd/python/sdd_reverse/analysis.reverse.template.md— si absent → STOP + ERROR[REVERSE_TEMPLATE_MISSING](ADV-9, pas de fallback inline).
Si {U-N} introuvable → STOP + ERROR [REVERSE_UNIT_NOT_FOUND] :
ERROR: reverse-tech-analyst {U-N} — unité introuvable
CAUSE: [REVERSE_UNIT_NOT_FOUND] units[id="{U-N}"] absent de workspace/old/{P}/.sys/inventory.json
FIX: lancer /sdd-reverse-inventory --refresh puis revérifier units[]
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.
- 2d ago First seen · 225 lines · 121 tokens per session scan A dcc794720d0d
reverse-tech-analyst is an agent published in the GitHub repository zekiriabd/SDD-Pro (187 stars, last pushed today), licensed Apache-2.0. It adds 121 tokens to every session and 3,692 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.