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.
git clone --depth 1 https://github.com/Jessinra/Lorekeepernpx agentmods add skills/jessinra/lorekeeper/backlog-managementWrote 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/jessinra/lorekeeper/backlog-management)<a href="https://agentmods.dev/skills/jessinra/lorekeeper/backlog-management"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/backlog-management/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/jessinra/lorekeeper/backlog-management"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/backlog-management.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.00043 | $0.01575 |
| Opus 5.5 | $0.00017 | $0.00630 |
| Sonnet 5.5 | $0.00009 | $0.00315 |
| Haiku 4.5 | $0.00004 | $0.00158 |
Grade A, and why
backlog-management 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Management
How tickets work in the Lorekeeper project. Every ticket has a lifecycle and a home.
Where Tickets Live
~/Code/lorekeeper/backlogs/
├── proposal/ # Raw ideas, S:Proposal
├── ready/ # Validated + prioritized, S:Ready
├── done/ # Shipped + verified, S:Done
├── cancelled/ # Won't do, S:Cancelled
└── TEMPLATE.md # Template
Tickets are PROPOSAL → READY → DONE (or CANCELLED). File location must match status — when status changes, git mv the file to the corresponding subdirectory. Zero files should live at backlogs/ root level.
Currently deferred tickets (S:Deferred) remain in proposal/ with the deferred label; they aren't ready for promotion but aren't dead either. Cancelled tickets are never reborn.
Ticket Lifecycle
S:proposal → S:ready → S:in-progress → S:review → S:done
↓
S:deferred / S:cancelled
| Status | Meaning | Who moves it | File location |
|---|---|---|---|
S:proposal |
Raw idea, not yet committed | Anyone | proposal/ |
S:ready |
Validated & prioritised, ready to work | PM | ready/ |
S:in-progress |
Being worked on | Dev | ready/ |
S:review |
Code done, pending PM review | Dev | ready/ |
S:done |
Shipped, verified | PM | done/ |
S:deferred |
Valid but not now | PM | proposal/ |
S:cancelled |
Won't do | PM | cancelled/ |
Numbering Convention
SEQUENTIAL only. Highest existing number + 1. Gaps are from done tickets moved to backlogs/done/. Never fill gaps.
Check all subdirectories (proposal/, ready/, done/, cancelled/) to find the highest number.
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 · 157 lines · 43 tokens per session scan A 09b8a8af3f2a
backlog-management is a skill published in the GitHub repository Jessinra/Lorekeeper (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,575 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
project-switching
Project switching implementation in sidecar: project discovery, state management, UI flow, modal rendering, filtering, theme preview, and plugin reinitialization. Use when working on the project switcher feature, project management, worktree switching, or the project configuration system.
board-pilot
Board-driven implementation pipeline: polls a GitHub Project, arms an item when dragged into the trigger column, advances it stage by stage to a human-gated draft PR. Stages configured per project in workflow/projects/ .yaml. Trigger: "/board-pilot", "board pilot", "auto-implement from board", "pipeline runner".
bridge-overlay
Subscribe a Bridge to an ORG OVERLAY: a git repo publishing shared config (contexts, projects, mandants, org skills) as a flat mirror tree. Materializes copies via 3-way merge; your files always win. Trigger: "/overlay", "org overlay", "subscribe to overlay", "overlay status", "overlay diff".
github-projects-manager
The only write path to GitHub Projects V2, plus its governance: issue creation with board placement, field updates, batch transitions, board queries, audits, health checks, new-board setup. Reads schemas and rules from workflow/projects/.yaml. Trigger: "create issue", "set field", "board query", "audit board", "board…
debrief
Meeting and transcript processing: classifies meeting type, name corrections, extracts insights, generates protocols, proposes tasks. Full 8-phase flow (GitHub reconciliation, distribution email) or quick 5-phase. Trigger: "/debrief", "/debrief {path}", "/debrief --quick", "/debrief --all", "/debrief --date…
task-close-postmortem
Postmortem capture and bridge-improvement scan at task close: surfaces optional questions (time invested, what went well, what burned time, bridge gaps), writes frontmatter to STATUS.md, and generates proposals under work/learning/proposals/ for review via /bridge-learn. Trigger: "task done", "wrap up", "post-mortem"…