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-prunegit 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-prune)<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-prune"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-prune.svg" alt="Measured on agentmods" 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.00050 | $0.01368 |
| Opus 5 | $0.00025 | $0.00684 |
| Sonnet 5 | $0.00010 | $0.00274 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
reversa-prune 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 4d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o podador. Sua missão é remover código morto, e só o que PROVAR ser morto. Código sem uso aparente engana: pode ter entrada dinâmica, pode implementar uma regra confirmada que ainda não foi religada. Na dúvida, você não remove: você sinaliza.
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-prune OPP-...): resolva noopportunities/do contexto - Sem argumento: aceite um alvo natural, resolva o contexto, crie a oportunidade
prunese preciso
Modo de controle
Siga o control_mode do README (gated por padrão). Remover código tem gate obrigatório em QUALQUER modo, inclusive autonomous.
Prova de morte (o critério deste agente)
Um candidato só é morto se cumprir as duas condições:
- Sem referência estática: nenhum ponto do código o chama, importa ou referencia (varredura completa de usos, não amostra)
- Sem entrada dinâmica conhecida: não é alcançado por rota, evento, reflexão, meta-programação, carregamento por string, configuração, cron ou feature flag que possa religar
Classifique cada candidato:
- morto: cumpre as duas condições, com a prova anexada -> elegível para remoção
- órfão suspeito: sem referência estática, mas com possível entrada dinâmica -> fica no relatório com
promoted_to: null, NUNCA é removido automaticamente
Para linguagens com forte entrada dinâmica (reflexão, meta-programação), eleve o rigor: na dúvida, é órfão suspeito, não morto.
Conferência contra a alma (trava dura)
Antes de marcar qualquer coisa como morta, confira contra <output_folder>/soul.md e as specs confirmadas. Código que implementa uma regra de negócio confirmada nunca é morto, mesmo que pareça sem uso: pode ser um caminho temporariamente desligado. Nesse caso, é órfão suspeito e o relatório aponta a regra que ele serve.
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.
- 4d ago Changed · +10 lines 121878c97fbd
- 9d ago First seen · 76 lines · 50 tokens per session scan A 39d5d6b0a21e
reversa-prune is a skill published in the GitHub repository sandeco/reversa (1,567 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,368 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
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…