add-backlog

add-backlog is a skill for Claude Code, Codex from buildomator/buildomator. It costs 17 tokens per session (587 once invoked), scanned A, original, MIT.

A procedure for adding an idea to a project backlog, the list of work reserved for later. It records the idea in the roadmap, creates a numbered phase directory, and commits those changes.

In plain words
What is it for?
Use it to park an unfinished idea, assign the next backlog number, create its planning directory, and record the change in version control.
Why use it?
It gives future work a stable name, location, and roadmap entry instead of leaving the idea in an untracked note. The numbering helps avoid duplicate backlog items.

Skill for Claude CodeCodex

Part of the gsd plugin — 86 skills, 33 agents, 6 hooks shipped together

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 skills/buildomator/buildomator/add-backlog
Any agent
npx skills add buildomator/buildomator --skill add-backlog
Clone the repo
git clone --depth 1 https://github.com/buildomator/buildomator

Made for: Claude Code, Codex.

Or install gsd, the plugin that ships this one along with the rest of its 86 skills, 33 agents, 6 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/buildomator/buildomator/add-backlog.svg)](https://agentmods.dev/skills/buildomator/buildomator/add-backlog)
Your own site
<a href="https://agentmods.dev/skills/buildomator/buildomator/add-backlog"><img src="https://agentmods.dev/badge/skills/buildomator/buildomator/add-backlog.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 587 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.00017 $0.00587
Opus 5 $0.00009 $0.00293
Sonnet 5 $0.00003 $0.00117
Haiku 4.5 $0.00002 $0.00059

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

Security

Grade A, and why

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 5d 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.

skills/add-backlog/SKILL.md · 76 lines

What it actually says

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

    cat .planning/ROADMAP.md
    
  2. Find next backlog number:

    NEXT=$(bm-sdk query phase.next-decimal 999 --raw)
    

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

  3. Add to ROADMAP.md under a ## Backlog section. If the section doesn't exist, create it at the end. Write the ROADMAP entry BEFORE creating the directory, so directory existence reliably means the phase is already registered (prevents false duplicate detection in hooks checking 999.x directories, #2280):

    ## Backlog
    
    ### Phase {NEXT}: {description} (BACKLOG)
    
    **Goal:** [Captured for future planning]
    **Requirements:** TBD
    **Plans:** 0 plans
    
    Plans:
    - [ ] TBD (promote with /gsd:review-backlog when ready)
    
  4. Create the phase directory:

    SLUG=$(bm-sdk query generate-slug "$ARGUMENTS" --raw)
    mkdir -p ".planning/phases/${NEXT}-${SLUG}"
    touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
    
  5. Commit:

    bm-sdk query commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" .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. 5d ago First seen · 76 lines · 17 tokens per session scan A ead324956878

Subscribe to this mod's changes

add-backlog is a skill published in the GitHub repository buildomator/buildomator (86 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 587 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.

Related

Other skills, from other repositories

agile-product-owner

../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.

alirezarezvani/claude-skills · 0 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

subagent-delegation

Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.

toonight/get-shit-done-for-antigravity · 42 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

project-init

Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…

BlackBeltTechnology/pi-agent-dashboard · 81 tokens