backlog-ticker

A narrowly scoped helper for updating one backlog entry, where a backlog is a list of planned tasks. It marks the supplied item complete and adds a supplied reference link.

In plain words
What is it for?
Use it when a documentation workflow needs to check off exactly one item and attach its reference.
Why use it?
It prevents accidental changes to nearby backlog text or unrelated files when recording one completed task.

Agent

Part of the craft plugin — 20 skills, 4 commands, 18 agents, 1 hook 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 agents/scolladon/craft/backlog-ticker
Clone the repo
git clone --depth 1 https://github.com/scolladon/craft

Or install craft, the plugin that ships this one along with the rest of its 20 skills, 4 commands, 18 agents, 1 hook.

Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 192 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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.00038 $0.00192
Opus 5 $0.00019 $0.00096
Sonnet 5 $0.00008 $0.00038
Haiku 4.5 $0.00004 $0.00019

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

Security

Grade A, and why

backlog-ticker 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 2d 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

This is a copy

92% identical to craft-backlog-ticker — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/backlog-ticker.md · 19 lines

What it actually says

You perform exactly one edit in exactly one file. Your invocation carries: the backlog file path, the exact entry line to change, and the exact reference suffix to append.

Contract:

  • Flip the entry's checkbox ([ ] or [~][x]) and append ONLY the provided reference suffix to that line.
  • You MUST NOT reword, rewrite, reorder, or annotate the entry body or any other line. No retrospective prose. The diff must touch exactly the expected line(s) — the session verifies and discards your work otherwise.
  • Do not commit; the session reviews the diff and commits.
  • Final message: the single line as it now reads.
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. 2d ago First seen · 19 lines · 38 tokens per session scan A cf7bf7781dc9

Subscribe to this mod's changes

backlog-ticker is an agent published in the GitHub repository scolladon/craft (2 stars, last pushed 14d ago), licensed MIT. It adds 38 tokens to every session and 192 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to craft-backlog-ticker, differing in 6 lines, and is treated as a copy.