A project backlog tool for storing ideas and tasks in a shared JSON file, then viewing, promoting, removing, and reconciling them.

Use it to capture an idea, inspect the backlog, move an entry into planned work, or remove completed or no-longer-needed items.

It keeps future work from being lost and connects backlog entries to the features and larger work areas they belong to.

backlog — Skill for Claude Code by infraspecdev/tesseract

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/infraspecdev/tesseract

agentmods

npx agentmods add skills/infraspecdev/tesseract/backlog

Made for: Claude Code.

Or install shield, the plugin that ships this one along with the rest of its 36 skills, 17 commands, 22 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/infraspecdev/tesseract/backlog/github.svg)](https://agentmods.dev/skills/infraspecdev/tesseract/backlog)

Your own site

<a href="https://agentmods.dev/skills/infraspecdev/tesseract/backlog"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/backlog/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/infraspecdev/tesseract/backlog"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,474 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.

Model	Per session	Once invoked
Fable 5.1	$0.00074	$0.02474
Opus 5.5	$0.00030	$0.00990
Sonnet 5.5	$0.00015	$0.00495
Haiku 4.5	$0.00007	$0.00247

Measured 1mo ago against content hash cbc548dec07e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

shield/skills/general/backlog/SKILL.md · 212 lines

How it starts

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

Backlog — capture, view, promote, reconcile

The Shield backlog is a single global JSON file at docs/shield/backlog.json that holds ideas captured at any point during Shield's research → prd → plan → implement pipeline. Each entry is associated with a feature (the reconciliation key) and an epic (the removal gate) — either may be proposed-new at capture time.

Output Paths — MANDATORY

Artifact	Path	Owner
Store	`docs/shield/backlog.json`	`shield/scripts/backlog_store.py`
Schema	`shield/schema/backlog.schema.json`	(this skill)
Validator	`shield/scripts/validate_backlog.py`	(this skill)
Suggester	`shield/backlog/shield_backlog/suggester.py`	(this skill)
Reconciler	`shield/backlog/shield_backlog/reconciler.py`	(this skill)
Removal log	`.shield/backlog-removed.log`	reconciler (append-only)
Kill switch	`.shield.json` → `backlog.auto_reconcile` (default `true`)	user

Entry shape (v1)

{
  "id":      "<uuid4>",          // generated by capture; uniqueness enforced by validator
  "order":   42,                 // integer; ascending = view order
  "kind":    "task",             // epic | story | task
  "source":  "user",             // user | agent
  "feature": "auth",             // existing folder slug OR proposed-new
  "epic":    "Session mgmt",     // existing epic NAME (plan.json.epics[].name) OR proposed-new
  "text":    "Rotate refresh tokens every 24h"
}

id contract

Format: uuid4 string (generated via uuid.uuid4()).
Why uuid4: collision-free capture with no read-before-write — multiple skills can mint an id without coordinating.
Uniqueness: enforced by validate_backlog.py (named error duplicate_entry_id), not by the JSON Schema. Draft 2020-12 uniqueItems is whole-item equality and cannot express property-level uniqueness.
Used as the key for: promotion (transient runtime arg), manual remove, eager prune, lazy sweep recovery (.shield/backlog-removed.log lookup).

Read the full file on GitHub · 212 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.

1mo ago First seen · 212 lines · 74 tokens per session scan A cbc548dec07e

Subscribe to this mod's changes

backlog is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 2,474 once invoked, about $0.0003 per session on Opus 5.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.

Project management

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

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

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 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

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

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

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens