revisar-backlog

revisar-backlog is a command for Claude Code from luanpdd/kit-mcp. It costs 17 tokens per session (561 once invoked), scanned A, original, MIT.

A backlog review command that lists deferred roadmap items and lets you promote, keep, or remove each one.

In plain words
What is it for?
Use it to inspect backlog descriptions and accumulated notes, move selected items into the active milestone with updated numbering, or delete items you no longer want.
Why use it?
It keeps postponed work visible and makes decisions about it explicit, instead of leaving old items disconnected from the active milestone.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it to inspect backlog descriptions and accumulated notes, move selected items into the active milestone with updated numbering, or delete items you no longer want.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/luanpdd/kit-mcp/revisar-backlog
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.

Clone the repo
git clone --depth 1 https://github.com/luanpdd/kit-mcp

Made for: Claude Code.

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 revisar-backlog

README.md
[![agentmods](https://agentmods.dev/badge/commands/luanpdd/kit-mcp/revisar-backlog.svg)](https://agentmods.dev/commands/luanpdd/kit-mcp/revisar-backlog)
Your own site
<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/revisar-backlog"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/revisar-backlog.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 561 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.00017 $0.00561
Opus 5 $0.00009 $0.00280
Sonnet 5 $0.00003 $0.00112
Haiku 4.5 $0.00002 $0.00056

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

Security

Grade A, and why

revisar-backlog 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.

kit/commands/revisar-backlog.md · 61 lines

What it actually says

  1. Listar itens do backlog:

    ls -d .planning/phases/999* 2>/dev/null || echo "Nenhum item de backlog encontrado"
    
  2. Ler ROADMAP.md e extrair todas as entradas de fase 999.x:

    cat .planning/ROADMAP.md
    

    Mostrar cada item do backlog com sua descrição, qualquer contexto acumulado (CONTEXT.md, RESEARCH.md) e data de criação.

  3. Apresentar a lista ao usuário via AskUserQuestion:

    • Para cada item do backlog, mostrar: número da fase, descrição, artefatos acumulados
    • Opções por item: Promover (mover para ativo), Manter (deixar no backlog), Remover (deletar)
  4. Para itens a PROMOVER:

    • Encontrar o próximo número de fase sequencial no milestone ativo
    • Renomear o diretório de 999.x-slug para {novo_num}-slug:
      NEW_NUM=$(node "./.claude/framework/bin/tools.cjs" phase add "${DESCRIPTION}" --raw)
      
    • Mover artefatos acumulados para o novo diretório de fase
    • Atualizar ROADMAP.md: mover entrada da seção ## Backlog para a lista de fases ativas
    • Remover marcador (BACKLOG)
    • Adicionar campo **Depends on:** apropriado
  5. Para itens a REMOVER:

    • Deletar o diretório da fase
    • Remover a entrada da seção ## Backlog do ROADMAP.md
  6. Commitar alterações:

    node "./.claude/framework/bin/tools.cjs" commit "docs: revisar backlog — promovidos N, removidos M" --files .planning/ROADMAP.md
    
  7. Relatório resumo:

    ## Revisão de Backlog Concluída
    
    Promovidos: {lista de itens promovidos com novos números de fase}
    Mantidos: {lista de itens que permanecem no backlog}
    Removidos: {lista de itens deletados}
    
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. 4d ago First seen · 61 lines · 17 tokens per session scan A 866a0b478e25

Subscribe to this mod's changes

revisar-backlog is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 561 once invoked, about $0.0001 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-09-03.