reversa-forward

reversa-forward is a skill for Codex from sandeco/reversa. It costs 84 tokens per session (4,105 once invoked), scanned A, original, MIT.

A routing guide for the forward development workflow in Reversa, a system for taking a feature from requirements through planning, coding, review, and synchronization.

In plain words
What is it for?
Use it to check feature status and find the next suitable step, such as clarifying requirements, making a plan, coding, auditing, or syncing.
Why use it?
It shows which stage an active feature has reached and prevents the next workflow step from being chosen blindly. It only routes the work and does not create project files.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Claude Code; mentions Codex; mentions Gemini CLI.

Good fit Use it to check feature status and find the next suitable step…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sandeco/reversa/reversa-forward
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,562 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-forward
Clone the repo
git clone --depth 1 https://github.com/sandeco/reversa

Made for: 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-forward

README.md
[![agentmods](https://agentmods.dev/badge/skills/sandeco/reversa/reversa-forward.svg)](https://agentmods.dev/skills/sandeco/reversa/reversa-forward)
Your own site
<a href="https://agentmods.dev/skills/sandeco/reversa/reversa-forward"><img src="https://agentmods.dev/badge/skills/sandeco/reversa/reversa-forward.svg" alt="Measured on agentmods" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,105 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.
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.00084 $0.04105
Opus 5 $0.00042 $0.02053
Sonnet 5 $0.00017 $0.00821
Haiku 4.5 $0.00008 $0.00411

Measured 7d ago against content hash e1165d3b5e2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

reversa-forward 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.

agents/reversa-forward/SKILL.md · 234 lines

How it starts

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

Você é o orquestrador do ciclo forward do Reversa. Sua missão é olhar o estado atual do projeto e da feature ativa, dizer ao usuário em que ponto do pipeline ele está e sugerir o próximo skill apropriado. Você NUNCA executa o próximo skill automaticamente, sempre encerra pedindo CONTINUAR.

Antes de começar

  1. Leia .reversa/state.json 1.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. user_name → nome para personalizar a saudação
  2. Quando o texto deste skill mencionar _reversa_sdd/ ou _reversa_forward/, use os valores reais resolvidos do state.json
  3. Se state.json não existir, trate como _reversa_sdd/ e _reversa_forward/ literais e siga adiante

Contexto de extração reversa

O pipeline forward funciona em dois cenários:

  1. Evolução de legado: existe _reversa_sdd/ com artefatos da extração reversa. Os skills do pipeline (especialmente /reversa-requirements e /reversa-plan) vão ancorar decisões nesses artefatos.
  2. Projeto novo (greenfield): não existe _reversa_sdd/ ainda. O pipeline forward continua valendo, só perde a ancoragem no legado.

NÃO bloqueie em nenhum caso. Verifique e prepare a estrutura seguindo as MESMAS regras de criação de pastas que o /reversa original aplica:

  1. Resolva os paths reais a partir de .reversa/state.json: 1.1. output_folder (padrão _reversa_sdd) 1.2. forward_folder (padrão _reversa_forward)
  2. Se a pasta output_folder existe e contém pelo menos um arquivo .md, registre internamente o cenário como legado e diga ao usuário: "Extração reversa detectada, o pipeline vai ancorar decisões em <output_folder>/."
  3. Se a pasta output_folder NÃO existe ou está vazia, registre internamente como greenfield e: 3.1. Crie a pasta <output_folder>/ (criação recursiva, equivalente a mkdir -p) 3.2. Crie também a pasta <forward_folder>/ se ainda não existir (pelo mesmo método) 3.3. NÃO crie nenhum arquivo dentro dessas pastas. Sem .gitkeep, sem placeholders. A pasta output_folder já está no .gitignore (gerenciado pelo installer), criar arquivos só introduziria ruído 3.4. NÃO altere .reversa/state.json#created_files nem .gitignore, isso é responsabilidade do installer e do /reversa original, não deste skill 3.5. Comunique ao usuário: "Sem extração reversa neste projeto, vou operar em modo greenfield. Criei <output_folder>/ e <forward_folder>/ para que os skills do pipeline possam escrever artefatos quando precisarem. Se quiser ancorar em legado depois, rode /reversa a qualquer momento."

Read the full file on GitHub · 234 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. 7d ago First seen · 234 lines · 84 tokens per session scan A e1165d3b5e2b

Subscribe to this mod's changes

reversa-forward is a skill published in the GitHub repository sandeco/reversa (1,562 stars, last pushed 3d ago), licensed MIT. It adds 84 tokens to every session and 4,105 once invoked, about $0.0004 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-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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens