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-standardizegit 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-standardize)<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-standardize"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-standardize/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-standardize"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-standardize.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.00036 | $0.01169 |
| Opus 5 | $0.00018 | $0.00584 |
| Sonnet 5 | $0.00007 | $0.00234 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
reversa-standardize 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o padronizador. Sua missão é aplicar convenções consistentes de nomenclatura, formatação, organização e escrita ao código, seguindo o padrão que o próprio projeto já pratica. É trabalho puramente cosmético e estrutural: você jamais muda semântica, fluxo ou comportamento.
Antes de começar
- Leia
.reversa/state.json(output_folder,chat_language,doc_language,user_name) - Leia
_reversa_refactor/README.md(control_mode). 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-standardize OPP-...): resolva noopportunities/do contexto - Sem argumento: aceite um alvo natural (arquivo, pasta, convenção), resolva o contexto, crie a oportunidade
standardizese preciso
Modo de controle
Siga o control_mode do README (gated por padrão): análise flui; todo passo que toca o código passa por gate com diff.
Detecção do padrão (antes de propor mudança)
- Analise o próprio código para descobrir o padrão dominante (nomenclatura, indentação, organização de arquivos, ordem de imports, convenções de comentário). Não imponha um estilo estranho ao projeto
- Se não houver padrão dominante claro, apresente ao usuário as opções encontradas em menu e deixe ele declarar o padrão alvo
- Prefira ferramentas idempotentes já do ecossistema do projeto (formatadores, linters já configurados) quando existirem, em vez de reescrita manual
Rede de segurança (proporcional)
Padronização é cosmética e dispensa testes de caracterização, MAS renomeações precisam preservar todas as referências. Trate renomeação como mudança que exige varredura completa de usos antes de aplicar; se a linguagem tiver renomeação segura por ferramenta, use-a. Se houver testes, rode-os depois como confirmação de que nada semântico mudou.
Fluxo
- Liste as inconsistências contra o padrão dominante ou declarado
- Agrupe em lotes coesos (por arquivo ou por convenção), para o usuário revisar em pedaços digeríveis
- Gate: mostre o diff de cada lote, aguarde aprovação, aplique. Mudança cosmética em massa NUNCA é aplicada em silêncio
- Confirme: se houver suíte de testes, rode e cole a saída verde como prova de que a padronização não mexeu na semântica
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 61876ab40993
- 7d ago First seen · 67 lines · 36 tokens per session scan A 4de9af588103
reversa-standardize is a skill published in the GitHub repository sandeco/reversa (1,579 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 1,169 once invoked, about $0.0002 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
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
platform-detection
Identify a .NET project's test platform, framework, command mode, and SDK-style vs classic project system. Use only for "which test platform/framework?", "VSTest or MTP?", or "what runner does this project use?", including bridge settings, UseVSTest opt-outs, and incompatible or conflicting VSTest/MTP configuration.…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
omh-rust
This is a Hermes-native rust workflow skill.
axiom-concurrency
Use when writing ANY async code, actors, threads, or seeing ANY concurrency error. Covers Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns.