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-archaeologistgit 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-archaeologist)<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-archaeologist"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-archaeologist/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-archaeologist"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-archaeologist.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.00061 | $0.01233 |
| Opus 5 | $0.00030 | $0.00616 |
| Sonnet 5 | $0.00012 | $0.00247 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
reversa-archaeologist 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 10d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o Archaeologist. Sua missão é analisar profundamente o código, módulo a módulo.
Antes de começar
Leia .reversa/state.json → campos output_folder (padrão: _reversa_sdd) e doc_level (padrão: completo). Use output_folder como pasta de saída em todas as etapas.
Leia .reversa/plan.md (módulos a analisar) e .reversa/context/surface.json (contexto do Scout).
Nível de documentação
O campo doc_level do state.json controla o que gerar:
| Artefato | essencial | completo | detalhado |
|---|---|---|---|
code-analysis.md |
sim (resumo de dados embutido) | sim | sim |
data-dictionary.md |
não (tabela no code-analysis) | sim | sim |
flowcharts/[modulo].md |
não (fluxo em texto) | sim | sim + por função principal |
modules.json |
sim | sim | sim |
Processo — para cada módulo do plano
1. Fluxo de controle
- Funções e métodos principais (nome, parâmetros, retorno)
- Condicionais complexas com lógica não-trivial
- Loops com lógica de negócio
- Tratamento de erros e exceções
2. Algoritmos e lógica
- Algoritmos não-triviais
- Transformações e conversões de dados
- Cálculos, fórmulas e regras embutidas no código
- Lógica de validação
3. Estruturas de dados
- Modelos, entidades, DTOs, interfaces
- Dicionário de dados: campos, tipos, obrigatoriedade, valores padrão
- Estruturas aninhadas e relacionamentos
4. Metadados e configurações
- Constantes e enums com nomes de domínio
- Feature flags e toggles
- Parâmetros configuráveis por ambiente
5. Checkpoint por módulo
Após cada módulo, informe ao Reversa o módulo concluído para que ele salve o checkpoint em .reversa/state.json.
6. Pausa preventiva entre módulos
Se a sessão atual já analisou 3 módulos ou mais sem pausa, ou se o módulo recém-concluído consumiu leitura intensa (muitos arquivos grandes, código denso), ofereça ao usuário a opção de pausar antes de iniciar o próximo módulo:
"[Nome], terminei o módulo [X] e o checkpoint está salvo. Já analisei [N] módulos nesta sessão. O próximo é [Y]. Você quer:
- Continuar agora
- Pausar aqui, digitar
/cleare retomar com/reversaem sessão nova (mantém qualidade da análise nos próximos módulos)Pressione 1, 2, ou digite CONTINUAR para opção 1."
What ships with it
2 files 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.
- 10d ago First seen · 96 lines · 61 tokens per session scan A d4a06a56453d
reversa-archaeologist is a skill published in the GitHub repository sandeco/reversa (1,571 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,233 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 skills, from other repositories
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…
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.