backlog

backlog is a skill for Claude Code, Codex from umputun/cc-thingz. It costs 96 tokens per session (3,201 once invoked), scanned A, original, MIT.

A Git-based list for deferred work: real defects, cleanup tasks, or ideas kept in one Markdown file per item under docs/backlog/.

In plain words
What is it for?
Use it to read, add, maintain, and close backlog items in a Git repository.
Why use it?
It keeps worthwhile work visible without mixing it into the current task or treating it as a release blocker.

Skill for Claude CodeCodex

Part of the workflow plugin — 6 skills 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/umputun/cc-thingz/backlog
Any agent
npx skills add umputun/cc-thingz --skill backlog
Clone the repo
git clone --depth 1 https://github.com/umputun/cc-thingz

Made for: Claude Code, Codex.

Or install workflow, the plugin that ships this one along with the rest of its 6 skills.

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 backlog

README.md
[![agentmods](https://agentmods.dev/badge/skills/umputun/cc-thingz/backlog.svg)](https://agentmods.dev/skills/umputun/cc-thingz/backlog)
Your own site
<a href="https://agentmods.dev/skills/umputun/cc-thingz/backlog"><img src="https://agentmods.dev/badge/skills/umputun/cc-thingz/backlog.svg" alt="Measured on agentmods" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,201 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.00096 $0.03201
Opus 5 $0.00048 $0.01600
Sonnet 5 $0.00019 $0.00640
Haiku 4.5 $0.00010 $0.00320

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

Security

Grade A, and why

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.

plugins/workflow/skills/backlog/SKILL.md · 198 lines

How it starts

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

Backlog

docs/backlog/ at a repo root holds work that is real but not being done now: a defect a change did not introduce, drift with no user-visible symptom, a fix whose blast radius exceeded its value, an idea worth keeping. One file per item. It is the maintainer's own list — it never gates anything and never reaches a contributor.

The directory path is fixed, so every invocation in a repo reads and writes one predictable store.

Git only. The lifecycle is expressed in Git — git rm to close an item, branch detection before writing, staging and committing the file. Outside a Git repository, say so plainly and stop; do not improvise an equivalent in another VCS.

Item format

docs/backlog/<slug>.md. The slug names the defect, not the file it lives in (reopen-fallback-ignores-frontmost.md), so it can be cited from a commit and dedupe is a filename check.

---
worth: later
where: internal/window/library.go:537
added: 2026-08-05
---
# reopen fallback ignores the last-frontmost window

`reopen`'s fallback ignores which window was last frontmost once `frontmost` is nil, so a multi-window
user's last-window capture replays only when the exited window happened to be `windows.first`. Surfaced
reviewing PR #370; the fix touches restore ordering, which is why it was deferred rather than done inline.

Three frontmatter fields, written once and rewritten only as Appending below allows:

  • worth: yes | no | later — the triage call, and the field the list is ordered by:
    • yes — the value is agreed and it should be fixed. Says nothing about schedule: an item blocked on an upstream release is still yes if nobody disputes it is worth doing.
    • later — the value decision itself is unresolved, not the work. The body must name the unknown or the condition that would settle it; without that it is a yes or a no in disguise.
    • no — a decision not to fix, kept so the same finding is not rediscovered and re-argued by the next review that touches the file. Keep a no only while that rationale still earns its place; once it does not, delete the file rather than carrying it.
  • where: path:line — omit when the item is not anchored to one place. Its path narrows the dedupe search alongside the slug and the line is a navigation hint that moves. Compare paths only when both items have where; two items missing it are not thereby the same item.
  • added: YYYY-MM-DD — never updated, so it reads as age. A year-old item is itself information. Zero-pad it so the values sort lexically.

Read the full file on GitHub · 198 lines

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 · 198 lines · 96 tokens per session scan A 40904cfa5690

Subscribe to this mod's changes

backlog is a skill published in the GitHub repository umputun/cc-thingz (465 stars, last pushed 11d ago), licensed MIT. It adds 96 tokens to every session and 3,201 once invoked, about $0.0005 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

flow-next-plan

Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).

gmickel/flow-next · 36 tokens

flow-next-tracker-sync

Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.

gmickel/flow-next · 44 tokens

st-setup-project

Smalltalk (Pharo/Squeak) project boilerplate creator. Use when the user asks to create a new Pharo/Smalltalk project from scratch, when project structure is missing (no src/ directory or .project file), when the user wants to start a new Smalltalk development project, or when setting up BaselineOf, Core, and Tests…

mumez/smalltalk-dev-plugin · 80 tokens

scheduler

Manage scheduled jobs — create, update, list, run remote agents on cron. Use when setting up recurring tasks, checking job status, or managing automation.

martineserios/thebrana · 33 tokens

do

Alias for /brana:backlog start with freeform text. Routes to the best skill or creates a task. Use /brana:backlog start directly for the same behavior.

martineserios/thebrana · 40 tokens

subtask-update

Update subtask with fixes or new steps. Two trigger modes: (A) Auto-called by autoworker:gate-check on FAIL — reads FAIL info, adds supplementary steps. (B) User calls with a finding/bug during testing — diagnoses, fixes, updates subtask. Both modes end by invoking autoworker:dispatch to re-enter the loop.

phj128/autoworker · 77 tokens