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.
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 skills add sandeco/reversa --skill reversa-debugger-fixgit clone --depth 1 https://github.com/sandeco/reversaWrote 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/skills/sandeco/reversa/reversa-debugger-fix)<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-debugger-fix"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-debugger-fix/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/skills/sandeco/reversa/reversa-debugger-fix"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-debugger-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.03558 |
| Opus 5.5 | $0.00028 | $0.01423 |
| Sonnet 5.5 | $0.00014 | $0.00712 |
| Haiku 4.5 | $0.00007 | $0.00356 |
Grade A, and why
reversa-debugger-fix 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o corretor. Sua missão é levar um bug registrado da triagem até o fechamento comprovado, mantendo a memória causal íntegra: causa raiz com evidência, testes que provam, mudanças rastreáveis e veredito de spec com decisão humana. Nem todo projeto passa por todas as etapas: a closure policy e o contexto definem o caminho.
Antes de começar
- Leia
.reversa/state.json(output_folder,chat_language,doc_language,user_name) - Leia
_reversa_bugs/README.md(closure policy, control_mode) e o schema emreferences/../reversa-debugger/references/bug-schema.mdse disponível; senão siga o contrato descrito no README do registro - Se
_reversa_bugs/não existir, aborte: "Não há registro de bugs neste projeto. Rode/reversa-debuggerprimeiro."
Seleção do bug
- Com argumento (
/reversa-debugger-fix BUG-20260715-A7K3ou/reversa-debugger-fix BUG-007): resolva por ID canônico oudisplay_number - O bug vive em
_reversa_bugs/<contexto>/bugs/: localize-o varrendo os catálogos de todos os contextos (_reversa_bugs/*/generated/catalog.jsonl, ou_reversa_bugs/*/bugs/*/bug.mdna falta deles). Se o usuário falou da área em linguagem natural ("conserta o carrinho"), comece pelo contexto correspondente. - Sem argumento: calcule o impact score sobre todos os contextos (só arestas
supported/confirmed) e sugira o bug de maior impacto sistêmico entre os abertos, explicando o porquê e dizendo o contexto. A escolha é do usuário (menu com top 3 + "Outro"). - Trava DONE: se existir
DONE.mdna pasta do bug, o bug está encerrado e é SOMENTE LEITURA. Recuse-se a mexer nele e explique as duas saídas: o usuário remover a trava manualmente (reabertura consciente) ou registrar um bug NOVO com relaçãoregression-ofapontando para o travado. Nunca remova a trava você mesmo. - Bug
resolvedsem trava, ou comblockingativo: informe e pergunte como proceder.
Modo de controle
Siga o control_mode do README (gated por padrão): leitura, reprodução isolada e diagnóstico fluem sem aprovação; TODO passo que altera o projeto passa por gate com diff. Em qualquer modo, têm gate obrigatório: alterar spec efetiva, enviar material a harness externo, operação destrutiva, reparo de dados.
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.
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 Changed · +10 lines 676203254c75
- 1mo ago Changed · +10 lines e65957ef5443
- 1mo ago First seen · 151 lines · 71 tokens per session scan A d7333b53570a
reversa-debugger-fix is a skill published in the GitHub repository sandeco/reversa (1,784 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 3,558 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.