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.
npx skills add adam-s-k-i/super-backlog --skill backlog-status-reportgit clone --depth 1 https://github.com/adam-s-k-i/super-backlogWrote 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.
[](https://agentmods.dev/skills/adam-s-k-i/super-backlog/backlog-status-report)<a href="https://agentmods.dev/skills/adam-s-k-i/super-backlog/backlog-status-report"><img src="https://agentmods.dev/badge/skills/adam-s-k-i/super-backlog/backlog-status-report/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.
<a href="https://agentmods.dev/skills/adam-s-k-i/super-backlog/backlog-status-report"><img src="https://agentmods.dev/badge/skills/adam-s-k-i/super-backlog/backlog-status-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.00298 |
| Opus 5 | $0.00023 | $0.00149 |
| Sonnet 5 | $0.00009 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
backlog-status-report 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 12d 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.
What it actually says
Backlog Status Report: project state at a glance
Read-only summary of the Backlog.md data in this project.
When this skill runs
- The user asks for status, progress, or an overview ("where are we?").
- Before or after a work session, to orient.
Procedure
- Read
backlog instructions overviewif not already loaded this session. - Collect data:
backlog task list --jsonplus milestones via the backlog CLI. - Report compactly in chat:
- Counts per status (To Do / In Progress / Done)
- Every In Progress task: ID, title, open acceptance criteria
- Milestones with done/total
- Blocked or stale items worth flagging
- Point to the visual surfaces:
sbl dashboard(live dashboard) orbacklog browser(interactive Kanban).
Boundaries
- Strictly read-only: never change task status, never edit tasks.
- Never guess state from memory — always read fresh CLI output.
- Keep the report short; link details instead of pasting them.
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.
- 12d ago Changed b48c519762e5
- 13d ago First seen · 33 lines · 47 tokens per session scan A 3e02a319c676
backlog-status-report is a skill published in the GitHub repository adam-s-k-i/super-backlog (2 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 298 once invoked, about $0.0002 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.
Other skills, from other repositories
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
git-workflow
Branching strategies, conventional commits, PR templates, and merge vs rebase guidance. Activate when starting features, creating PRs, or managing releases.
ratchet-recommend
Turn a ratchet BACKLOG.md + Ledger into a prioritized, model-routed execution plan (ratchet/NEXT.md) — what to do next, who should do each item (an autonomous cheap model, a supervised cheap model, a senior model, or a human decision), in what order, and with what verification. Read-only. Changes no code, no items, no…
planning-and-task-breakdown
Use when a spec or requirements exist and need to be broken into verifiable tasks with acceptance criteria. Explicit decomposition into tasks with clear definitions of done. Distinct from writing-plans which is output-focused.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".