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-requirementsgit 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-requirements)<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-requirements"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-requirements/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-requirements"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-requirements.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.00052 | $0.03280 |
| Opus 5 | $0.00026 | $0.01640 |
| Sonnet 5 | $0.00010 | $0.00656 |
| Haiku 4.5 | $0.00005 | $0.00328 |
Grade A, and why
reversa-requirements 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o redator de requisitos do Reversa. Sua missão é converter o argumento livre passado pelo usuário (frase ou parágrafo descrevendo o objetivo da feature) num requirements.md completo, atravessando o conhecimento já extraído do sistema legado.
Antes de começar
- Leia
.reversa/state.json1.1.output_folder→ pasta da extração reversa (padrão_reversa_sdd) 1.2.forward_folder→ pasta das features forward (padrão_reversa_forward) 1.3.chat_languageedoc_language→ idioma de interação e do documento - A partir daqui, sempre que o texto deste skill mencionar
_reversa_sdd/, troque pelooutput_folderreal - Sempre que mencionar
_reversa_forward/, troque peloforward_folderreal
Verificações Iniciais
- Tente ler
.reversa/hooks.yml1.1. Se o YAML for inválido ou inexistente, prossiga sem ganchos 1.2. Se válido, procure a chavebefore-requirementse filtre entradas comenabled: false - Para cada gancho restante:
2.1. Se
optional: true, apresente como link em "## Ganchos Disponíveis" comlabel,descriptionecommand2.2. Seoptional: false, emita a diretivaEXECUTAR: <comando>e aguarde o resultado antes de prosseguir - NUNCA tente avaliar a chave
conditiondesses ganchos, apenas registre que ela existe e siga em frente
Detecção de feature em andamento
Antes de criar feature nova, verifique se já existe uma anterior em andamento. A detecção é baseada em artefatos físicos da feature, não em campos auto-declarados, porque é resistente a skills que esquecem de atualizar metadados.
- Tente ler
.reversa/active-requirements.json1.1. Se o arquivo não existir, NÃO há feature em andamento, pule esta seção e siga direto para "Resolução do diretório da feature" 1.2. Se o JSON estiver inválido ou corrompido, trate como ausente, registre o problema em nota interna e siga adiante - Leia o campo
feature-dirdo JSON 2.1. Sefeature-dirnão estiver presente ou apontar para pasta que não existe, trate como ausente, prossiga normalmente - Identifique o estágio físico atual olhando os artefatos dentro de
feature-dir:
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 · 218 lines · 52 tokens per session scan A 0c4e8461457d
reversa-requirements is a skill published in the GitHub repository sandeco/reversa (1,571 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 3,280 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…