agentmods.dev

gsd:add-backlog

A command that saves an idea or future task in a project backlog, a list of work not yet scheduled. It creates a numbered backlog phase and updates the roadmap.

In plain words
What is it for?
Use it when a task is worth recording but is not ready to plan. It creates the backlog entry, a placeholder phase directory, and a commit.
Why use it?
It keeps useful ideas out of the active work while preserving them for later review. This avoids losing tasks or interrupting the current plan.

Command for Claude Code

160 11d ago A scan 19 tokens original MIT
View the source file kryptobaseddev/cleo
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.

agentmods
npx agentmods add commands/kryptobaseddev/cleo/add-backlog
Clone the repo
git clone --depth 1 https://github.com/kryptobaseddev/cleo

Made for: Claude Code.

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 635 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00019 $0.00635
Opus 5 $0.00010 $0.00318
Sonnet 5 $0.00004 $0.00127
Haiku 4.5 $0.00002 $0.00064

Measured yesterday against content hash c1e4ba3ee248, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gsd:add-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 yesterday.

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.

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

What it actually says

  1. Read ROADMAP.md to find existing backlog entries:

    cat .planning/ROADMAP.md

  2. Find next backlog number:

    NEXT=$(node "/tmp/pomodoro-bench/gsd/.claude/get-shit-done/bin/gsd-tools.cjs" phase next-decimal 999 --raw)

    If no 999.x phases exist, start at 999.1.

  3. Create the phase directory:

    SLUG=$(node "/tmp/pomodoro-bench/gsd/.claude/get-shit-done/bin/gsd-tools.cjs" generate-slug "$ARGUMENTS" --raw)
mkdir -p ".planning/phases/${NEXT}-${SLUG}"
touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"

  4. Add to ROADMAP.md under a ## Backlog section. If the section doesn't exist, create it at the end:

    ## Backlog

### Phase {NEXT}: {description} (BACKLOG)

**Goal:** [Captured for future planning]
**Requirements:** TBD
**Plans:** 0 plans

Plans:
- [ ] TBD (promote with /gsd-review-backlog when ready)

  5. Commit:

    node "/tmp/pomodoro-bench/gsd/.claude/get-shit-done/bin/gsd-tools.cjs" commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" --files .planning/ROADMAP.md ".planning/phases/${NEXT}-${SLUG}/.gitkeep"

  6. Report:

    ## 📋 Backlog Item Added

Phase {NEXT}: {description}
Directory: .planning/phases/{NEXT}-{slug}/

This item lives in the backlog parking lot.
Use /gsd-discuss-phase {NEXT} to explore it further.
Use /gsd-review-backlog to promote items to active milestone.
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. yesterday First seen · 77 lines · 19 tokens per session scan A c1e4ba3ee248

Subscribe to this mod's changes

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

Git and workflowPlanningProject management
Related

Other commands, from other repositories

advisor

Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.

koolamusic/claudefiles · 41 tokens

guide

You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.

rjwalters/kicad-tools · 0 tokens

pm-review

Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.

wei63w/pm-manager · 19 tokens

new

Creates a new item in a module that supports the new capability.

claudiodangelis/banco · 0 tokens

card

Open one self-contained OverClick card.

ustoppble/overclick · 8 tokens

linear-bulk

Apply the same change to many Linear issues at once. Dry-run by default.

Elnora-AI/elnora-linear · 20 tokens