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-simplifygit 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-simplify)<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-simplify"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-simplify/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-simplify"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-simplify.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.00053 | $0.01322 |
| Opus 5 | $0.00026 | $0.00661 |
| Sonnet 5 | $0.00011 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
reversa-simplify 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 7d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o simplificador. Sua missão é trocar uma lógica complexa por uma solução mais simples e clara, sem mudar o resultado. Seu objetivo primário é reduzir a complexidade cognitiva de quem lê a lógica; costuma reduzir também o custo de recurso, mas isso é efeito colateral, não a meta.
Antes de começar
- Leia
.reversa/state.json(output_folder,chat_language,doc_language,user_name) - Leia
_reversa_refactor/README.md(control_mode,safety_net_policy). Se_reversa_refactor/não existir, aborte: "Rode/reversa-refactorprimeiro." - Converse em
chat_language; escreva artefatos emdoc_language; nunca use travessão
Seleção da oportunidade
- Com argumento (
/reversa-simplify OPP-...): resolva noopportunities/do contexto - Sem argumento: aceite um alvo natural, resolva o contexto, crie a oportunidade
simplifyse preciso - Se o alvo real é ganho de desempenho medido (não clareza da lógica), reencaminhe a
/reversa-optimize
Modo de controle
Siga o control_mode do README (gated por padrão): análise e prova fluem; todo passo que toca o código passa por gate com diff.
Rede de segurança e equivalência (obrigatórias antes de tocar o código)
- Exija testes que fixem a saída do alvo; sem cobertura, ofereça testes de caracterização verdes antes de simplificar
- Equivalência de saída: comprove que o algoritmo simples produz a mesma saída para o mesmo conjunto de entradas, incluindo edge cases (vazio, nulo, limites, concorrência). Simplificar que muda um edge case não é simplificação, é bug
- Recusada a rede, rebaixe para 🔴 e registre a ausência de prova
Preservação de comportamento
Consulte <output_folder>/soul.md e as specs confirmadas. Uma lógica complexa às vezes esconde uma regra de negócio confirmada (caso especial que existe por um motivo). Antes de simplificar, verifique se a complexidade é acidental (dá para remover) ou essencial (a regra exige). Complexidade essencial não é simplificada; é documentada.
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.
- 7d ago Changed · +10 lines 1a4cd617e8b1
- 7d ago First seen · 70 lines · 53 tokens per session scan A cf5f3f0d8fd6
reversa-simplify is a skill published in the GitHub repository sandeco/reversa (1,579 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 1,322 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-09-03.
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.