Borrowing it
Nothing to install: this file belongs to zekiriabd/SDD-Pro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zekiriabd/SDD-Pro/main/.claude/agents/reverse-tech-analyst.mdgit 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/agents/zekiriabd/sdd-pro/reverse-tech-analyst)<a href="https://agentmods.dev/agents/zekiriabd/sdd-pro/reverse-tech-analyst"><img src="https://agentmods.dev/badge/agents/zekiriabd/sdd-pro/reverse-tech-analyst/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/agents/zekiriabd/sdd-pro/reverse-tech-analyst"><img src="https://agentmods.dev/badge/agents/zekiriabd/sdd-pro/reverse-tech-analyst.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.00121 | $0.03692 |
| Opus 5.5 | $0.00048 | $0.01477 |
| Sonnet 5.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 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.
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.
- 1mo 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 (196 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 121 tokens to every session and 3,692 once invoked, about $0.0005 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 agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…