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 agentmods add skills/jessinra/lorekeeper/backlog-managementnpx skills add Jessinra/Lorekeeper --skill backlog-managementgit clone --depth 1 https://github.com/Jessinra/LorekeeperWrote 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.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00788 |
| Sonnet 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 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.
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.
- 5d ago First seen · 157 lines · 43 tokens per session scan A 09b8a8af3f2a
backlog-management is a skill published in the GitHub repository Jessinra/Lorekeeper (4 stars, last pushed 1mo 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. 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
hs-release
Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
create-plugin
Create new sidecar plugins implementing the plugin.Plugin interface, rendering views with Bubble Tea, handling keyboard input via keymap contexts, and integrating with the app shell (footer hints, event bus, adapters). Use when creating a new plugin, modifying plugin architecture, or debugging plugin…
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
keyboard-shortcuts
Reference for keyboard shortcut implementation, keybinding registration, shortcut parity with vim and other TUI tools, and the complete shortcut assignment table across all sidecar plugins. Use when adding or modifying keyboard shortcuts, checking shortcut assignments, resolving key conflicts, or assessing alignment…
memory-audit-pattern-extraction
模式提取与失效解药分析。当发现多条记忆在讲同一个教训，或发现自己在一而再再而三地犯同样的错误时使用。.