What is reversa-debugger-graph?

A generator for views of recorded bugs, using the bug records as its single source of truth. It validates their consistency and creates indexes, relationship tables, a Mermaid diagram, and links between bugs and specifications.

Use it to regenerate bug catalogs, bug-to-bug relationships, diagrams, and bug-to-specification traceability for one feature area or the whole project.

It lets teams see the overall defect landscape without opening hundreds of individual files. Validation also exposes inconsistent or duplicate records instead of silently changing them.

reversa-debugger-graph — Skill for Claude Code and Codex by sandeco

About the project

Reversa is a reverse-engineering framework that analyzes legacy software and turns its hidden business rules, code flows, and architectural decisions into executable specifications for AI coding agents. Teams use it to help agents safely understand and change systems that lack reliable documentation. The catalogue skills provide the specialized agent workflows used to perform this analysis.

sandeco/reversa · 1,784 stars · on GitHub

Install

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.

Any agent

npx skills add sandeco/reversa --skill reversa-debugger-graph

Clone the repo

git clone --depth 1 https://github.com/sandeco/reversa

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sandeco/reversa/reversa-debugger-graph/github.svg)](https://agentmods.dev/skills/sandeco/reversa/reversa-debugger-graph)

Your own site

<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-debugger-graph"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-debugger-graph/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-debugger-graph"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-debugger-graph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,865 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00054	$0.01865
Opus 5.5	$0.00022	$0.00746
Sonnet 5.5	$0.00011	$0.00373
Haiku 4.5	$0.00005	$0.00186

Measured 1mo ago against content hash 4375f382228c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

reversa-debugger-graph 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.

agents/reversa-debugger-graph/SKILL.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Você é o cartógrafo dos defeitos. Os bug.md são a única fonte de verdade; sua missão é validá-los e regenerar todas as projeções de forma determinística, para que humanos e agentes enxerguem o panorama sem ler 200 arquivos. Você nunca edita um bug: se algo está inconsistente, você para e reporta.

Antes de começar

Leia .reversa/state.json (output_folder, doc_language)
Os bugs vivem agrupados por contexto: _reversa_bugs/<contexto>/bugs/. Se nenhuma pasta de contexto existir, informe que não há bugs registrados e aponte /reversa-debugger
Escopo: com argumento (/reversa-debugger-graph carrinho-de-compras), regenere só aquele contexto; sem argumento, regenere TODOS os contextos encontrados, um a um

Etapa 1: varredura e validação

Leia o front matter de TODOS os _reversa_bugs/*/bugs/*/bug.md (só o front matter; corpo apenas quando precisar de detalhe). A validação de invariantes é sempre GLOBAL, cruzando contextos (ID duplicado entre contextos é erro)
Valide as invariantes. Divergência é ERRO EXPLÍCITO, nunca conserto silencioso:
- ID duplicado (pode acontecer via merge de branches)
- schema_version desconhecida
- status: resolved sem resolution_kind ou sem closure.satisfied: true
- resolution_kind: fixed sem root_cause.state: confirmed, sem regression_tests ou sem spec_verdict
- Relação com ID inexistente, autorrelação, ciclo de duplicate-of
- DONE.md presente com status diferente de resolved (trava sem fechamento), ou resolved + closure.satisfied: true sem DONE.md (fechamento sem trava)
Havendo erros: liste todos (bug, campo, problema), gere as views apenas dos bugs válidos, marque os inválidos numa seção "Inconsistências" do index e pare o relatório nisso. Consertar é decisão humana.

Etapa 2: views em `<contexto>/generated/`

Cada contexto tem as próprias views em _reversa_bugs/<contexto>/generated/, cobrindo só os bugs daquele contexto (relações que cruzam contextos aparecem com o contexto do alvo indicado). Todas com cabeçalho . Escrita atômica. Crie generated/ do contexto se ainda não existir.

Read the full file on GitHub · 95 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 176 B

Changes

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 · 95 lines · 54 tokens per session scan A 4375f382228c

Subscribe to this mod's changes

reversa-debugger-graph is a skill published in the GitHub repository sandeco/reversa (1,784 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,865 once invoked, about $0.0002 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.

Debugging

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens