gsd:review-backlog

gsd:review-backlog is a command for Claude Code from kryptobaseddev/cleo. It costs 15 tokens per session (530 once invoked), scanned A, original, MIT.

A backlog-management workflow for reviewing deferred roadmap items and promoting, keeping, or removing them.

In plain words
What is it for?
Use it to inspect backlog descriptions and context, then move selected items into the active project roadmap.
Why use it?
It helps turn postponed work into active phases or clear it from the backlog when priorities change.

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 context, then move selected items…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kryptobaseddev/cleo/review-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/kryptobaseddev/cleo

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 gsd:review-backlog

README.md
[![agentmods](https://agentmods.dev/badge/commands/kryptobaseddev/cleo/review-backlog.svg)](https://agentmods.dev/commands/kryptobaseddev/cleo/review-backlog)
Your own site
<a href="https://agentmods.dev/commands/kryptobaseddev/cleo/review-backlog"><img src="https://agentmods.dev/badge/commands/kryptobaseddev/cleo/review-backlog.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 530 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.00015 $0.00530
Opus 5 $0.00008 $0.00265
Sonnet 5 $0.00003 $0.00106
Haiku 4.5 $0.00002 $0.00053

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

Security

Grade A, and why

gsd:review-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 3d 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.cleo/agent-outputs/T-POMODORO-BENCH-2026-04-16/gsd/.claude/commands/gsd/review-backlog.md · 63 lines

What it actually says

  1. List backlog items:

    ls -d .planning/phases/999* 2>/dev/null || echo "No backlog items found"
    
  2. Read ROADMAP.md and extract all 999.x phase entries:

    cat .planning/ROADMAP.md
    

    Show each backlog item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.

  3. Present the list to the user via AskUserQuestion:

    • For each backlog item, show: phase number, description, accumulated artifacts
    • Options per item: Promote (move to active), Keep (leave in backlog), Remove (delete)
  4. For items to PROMOTE:

    • Find the next sequential phase number in the active milestone
    • Rename the directory from 999.x-slug to {new_num}-slug:
      NEW_NUM=$(node "/tmp/pomodoro-bench/gsd/.claude/get-shit-done/bin/gsd-tools.cjs" phase add "${DESCRIPTION}" --raw)
      
    • Move accumulated artifacts to the new phase directory
    • Update ROADMAP.md: move the entry from ## Backlog section to the active phase list
    • Remove (BACKLOG) marker
    • Add appropriate **Depends on:** field
  5. For items to REMOVE:

    • Delete the phase directory
    • Remove the entry from ROADMAP.md ## Backlog section
  6. Commit changes:

    node "/tmp/pomodoro-bench/gsd/.claude/get-shit-done/bin/gsd-tools.cjs" commit "docs: review backlog — promoted N, removed M" --files .planning/ROADMAP.md
    
  7. Report summary:

    ## 📋 Backlog Review Complete
    
    Promoted: {list of promoted items with new phase numbers}
    Kept: {list of items remaining in backlog}
    Removed: {list of deleted items}
    
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. 3d ago First seen · 63 lines · 15 tokens per session scan A fec98e822654

Subscribe to this mod's changes

gsd:review-backlog is a command published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 17d ago), licensed MIT. It adds 15 tokens to every session and 530 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.