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-resumegit 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-resume)<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-resume"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-resume/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-resume"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-resume.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.00057 | $0.01743 |
| Opus 5 | $0.00028 | $0.00872 |
| Sonnet 5 | $0.00011 | $0.00349 |
| Haiku 4.5 | $0.00006 | $0.00174 |
Grade A, and why
reversa-resume 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o retomador. Sua missão é trocar a feature ativa por uma das que estão em paused-features, sem perder o trabalho de nenhuma das duas.
Antes de começar
- Leia
.reversa/state.jsonpara resolveroutput_foldereforward_folder - Use os valores reais nos lugares onde o texto mencionar
_reversa_sdd/ou_reversa_forward/
Verificações Iniciais
-
Leia
.reversa/active-requirements.json1.1. Se ausente, aborte com mensagem:> 🛑 `/reversa-resume` exige uma feature ativa para fazer a troca. `active-requirements.json` não existe. > > Use `/reversa-requirements` para criar a primeira feature do projeto. -
Verifique o campo
paused-features2.1. Se ausente ou array vazio, aborte com mensagem:> 🛑 Não há features pausadas para retomar. O array `paused-features` está vazio. > > Features ficam pausadas quando você roda `/reversa-requirements` numa feature ativa em andamento e escolhe a opção 2 (criar paralela). -
Aplique ganchos
before-resumeda forma padrão (lê.reversa/hooks.yml, filtraenabled: false, mesma lógica de outros skills do ciclo forward)
Listagem das pausadas
Para cada entrada em paused-features:
-
Verifique se o
feature-dirainda existe em disco 1.1. Se NÃO existir, marque comoausente(a pasta foi apagada manualmente, a entry virou lixo) -
Se existir, detecte o estágio físico atual com a mesma lógica do
/reversa-requirements:Condição observada em feature-dirEstágio físico requirements.mdausentevaziorequirements.mdpresente,roadmap.mdausenterequirementsroadmap.mdpresente,actions.mdausenteplanactions.mdpresente com pelo menos uma linha| ... | \[ \] |coding-em-progressoactions.mdpresente, todas as ações como| ... | \[X\] |done -
Para
coding-em-progresso, conte ações[X]versus[ ]
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.
- 10d ago First seen · 142 lines · 57 tokens per session scan A c0ef4fa9e7af
reversa-resume is a skill published in the GitHub repository sandeco/reversa (1,571 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 1,743 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.