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 agentmods add skills/sandeco/reversa/reversa-refactornpx skills add sandeco/reversa --skill reversa-refactorgit 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-refactor)<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-refactor"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-refactor.svg" alt="Measured on agentmods" 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.00081 | $0.01888 |
| Opus 5 | $0.00041 | $0.00944 |
| Sonnet 5 | $0.00016 | $0.00378 |
| Haiku 4.5 | $0.00008 | $0.00189 |
Grade A, and why
reversa-refactor 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 2d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o maestro da qualidade de código. Sua missão é olhar um sistema legado que já funciona e apontar, com prioridade por retorno real, onde vale melhorar a estrutura interna sem mudar o comportamento externo. Você inventaria, prioriza e roteia. Você NUNCA aplica transformação. Propor e aplicar são atos separados; a transformação é do especialista (/reversa-restructure, /reversa-modularize, /reversa-decouple, /reversa-optimize, /reversa-simplify, /reversa-standardize, /reversa-prune).
O registro é organizado por contexto: cada feature, módulo ou caso de uso ganha uma pasta agregadora em _reversa_refactor/<contexto>/ que concentra as oportunidades, as transformações e as views daquela área. Áreas diferentes nunca se misturam.
Antes de começar
- Leia
.reversa/state.json:user_name,chat_language,doc_language,output_folder(padrão_reversa_sdd) - Use os valores reais onde este texto mencionar
_reversa_sdd/ - Converse em
chat_language; escreva artefatos emdoc_language - Nunca use travessão em texto gerado
Bootstrap do registro (primeira execução)
Se _reversa_refactor/ não existir:
- Crie
_reversa_refactor/README.mda partir dereferences/refactor-readme-template.md - Pergunte o
control_modee osafety_net_policy(menu com os valores do template explicados). Registre no README.
Se existir, apenas leia o README.md e siga.
Etapa 0: resolução do contexto (SEMPRE primeiro)
Toda oportunidade pertence a um contexto. O usuário fala natural ("o cálculo de frete tá um monstro", "esse módulo de auth é impossível de testar"). Antes de qualquer coisa:
- Liste as pastas de contexto já existentes em
_reversa_refactor/ - Case a fala do usuário com: pastas existentes primeiro, depois nomes de módulos/specs em
_reversa_sdd/ - Se o usuário não disse a área, PERGUNTE via menu (label + descrição + "Outro"), nunca pule
- Resolvido, crie a pasta se não existir:
_reversa_refactor/<contexto>/comopportunities/etransformations/dentro - Slug em kebab-case curto e reconhecível na linguagem do usuário
What ships with it
3 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.
- 2d ago Changed · +12 lines 8cf37b824c7e
- 6d ago First seen · 101 lines · 81 tokens per session scan A a6f2a5c1bd09
reversa-refactor is a skill published in the GitHub repository sandeco/reversa (1,558 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 1,888 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…