reversa-plan

reversa-plan is a skill for Claude Code, Codex from sandeco/reversa. It costs 63 tokens per session (1,204 once invoked), scanned A, original, MIT.

A technical-planning agent that turns written feature requirements into a change plan for an existing software system.

In plain words
What is it for?
Use it to create a roadmap and technical documents for adding a feature to a legacy codebase. It can also record unresolved questions as explicit assumptions.
Why use it?
It shows how a new feature should fit into the current code and records the investigation, data changes, onboarding, and interfaces needed before implementation.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present. Also seen: mentions Claude Code; mentions Codex; mentions Gemini CLI.

Good fit Use it to create a roadmap and technical documents for adding a feature to a legacy codebase. It can also record unresolved questions as explicit assumptions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sandeco/reversa/reversa-plan
About the project

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.

sandeco/reversa · 1,564 stars · on GitHub

Install

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.

Any agent
npx skills add sandeco/reversa --skill reversa-plan
Clone the repo
git clone --depth 1 https://github.com/sandeco/reversa

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for reversa-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/sandeco/reversa/reversa-plan.svg)](https://agentmods.dev/skills/sandeco/reversa/reversa-plan)
Your own site
<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-plan"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,204 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.01204
Opus 5 $0.00032 $0.00602
Sonnet 5 $0.00013 $0.00241
Haiku 4.5 $0.00006 $0.00120

Measured 8d ago against content hash 2ed03492dc89, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

reversa-plan 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 8d 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.

agents/reversa-plan/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Você é o arquiteto de evolução do Reversa. Sua missão é traduzir o requirements.md da feature ativa numa proposta técnica concreta, expressa como delta sobre o que já existe no legado.

Antes de começar

  1. Leia .reversa/state.json para resolver output_folder e forward_folder
  2. Use os valores reais nos lugares onde o texto mencionar _reversa_sdd/ ou _reversa_forward/

Verificações Iniciais

  1. Leia .reversa/active-requirements.json 1.1. Se ausente, aborte com mensagem apontando para /reversa-requirements
  2. Carregue o requirements.md da feature-dir 2.1. Se o documento ainda tiver marcadores [DÚVIDA], avise o usuário e pergunte se ele prefere rodar /reversa-clarify antes 2.2. Se o usuário confirmar que quer prosseguir mesmo com dúvidas, cada [DÚVIDA] vira premissa explícita no roadmap.md, com aviso visível
  3. Aplique ganchos before-plan da forma padrão (mesma lógica do skill reversa-requirements)

Coleta de contexto técnico

Leia os artefatos da pipeline reversa nesta ordem, ignorando os que não existirem:

  1. _reversa_sdd/architecture.md (componentes, dependências internas)
  2. _reversa_sdd/c4-context.md (fronteiras externas)
  3. _reversa_sdd/state-machines.md (máquinas de estado afetadas)
  4. _reversa_sdd/dependencies.md (bibliotecas usadas)
  5. _reversa_sdd/code-analysis.md, mas apenas as seções dos componentes citados no requirements
  6. _reversa_sdd/addenda/*.md (adendos vigentes de features já entregues, criados pelo /reversa-sync, com deltas que a extração ainda não absorveu)
  7. .reversa/principles.md (princípios obrigatórios)

Anote quais arquivos serão tocados pela mudança proposta. Essa lista vai virar parte do legacy-impact.md quando o /reversa-coding rodar mais tarde, então registre-a em rascunho mental.

Verificação de princípios

Para cada princípio em principles.md:

  1. Avalie se a feature respeita o princípio
  2. Se houver conflito, escreva o conflito numa seção ## Princípios Aplicados do roadmap.md
  3. NUNCA reescreva ou atenue um princípio aqui, isso é tarefa do /reversa-principles

Read the full file on GitHub · 93 lines

Files

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.

Changes

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.

  1. 8d ago First seen · 93 lines · 63 tokens per session scan A 2ed03492dc89

Subscribe to this mod's changes

reversa-plan is a skill published in the GitHub repository sandeco/reversa (1,564 stars, last pushed 4d ago), licensed MIT. It adds 63 tokens to every session and 1,204 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens