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/greglas75/zuvo/backlognpx skills add greglas75/zuvo --skill backloggit clone --depth 1 https://github.com/greglas75/zuvoWhat 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 | $0.00085 | $0.03360 |
| Opus 5 | $0.00043 | $0.01680 |
| Sonnet 5 | $0.00017 | $0.00672 |
| Haiku 4.5 | $0.00009 | $0.00336 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:backlog — Tech Debt Management
Add, list, and manage backlog items. The backlog tracks technical debt discovered by audit skills, review agents, and manual entries.
Backlog location: memory/backlog.md at the MAIN checkout root — resolve worktree-safe per ../../shared/includes/backlog-protocol.md ("Where the Backlog Lives"), full canonical block (copy BOTH lines — the fallback is mandatory, without it a non-git CWD yields MAIN_ROOT="" and re-forks the backlog):
MAIN_ROOT=$(git worktree list --porcelain 2>/dev/null | head -1 | sed 's/^worktree //')
[ -z "$MAIN_ROOT" ] && MAIN_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
NEVER create or write a memory/backlog.md inside a linked worktree — one backlog per repository. If memory/ does not exist at MAIN_ROOT, create it. If the file does not exist, create it from the template at the bottom of this skill. If a legacy worktree-local copy exists, merge its unique entries (by Fingerprint) into the main copy before proceeding.
Scope: Managing the tech debt backlog -- viewing, adding, resolving, prioritizing, and suggesting batch actions.
Out of scope: Actually fixing the issues (use zuvo:fix-tests, zuvo:refactor, or the suggested command from suggest mode).
Argument Parsing
| Input | Action |
|---|---|
(empty) or list |
Show all OPEN items as a summary table |
list category:[x] |
Show OPEN items filtered by category (code/test/arch/dep/doc/infra) |
list all |
Show all items including RESOLVED and WONTFIX |
add |
Interactive: ask what to add, then append |
add [description] |
Parse natural language description, add to backlog |
fix B-{N} |
Mark item as RESOLVED |
wontfix B-{N} [reason] |
Mark item as WONTFIX with reason |
delete B-{N} |
Remove item (show details, ask confirmation) |
delete B-{N} --force |
Remove without confirmation |
delete all-resolved |
Remove all RESOLVED + WONTFIX items (ask confirmation) |
stats |
Show counts by severity and category |
prioritize |
Score and rank all OPEN items by urgency |
suggest |
Group items by pattern, propose batch fix commands |
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.
- 2d ago First seen · 333 lines · 85 tokens per session scan A 2b4a35f1dbc9
backlog is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 3,360 once invoked, about $0.0004 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
orchestrate
Use this agent when you need rigorous project management following the NASAB framework principles.
ds-freeze
Release scope triage — collaboratively decide which features ship this release vs defer to backlog, file/implement the kept set, sync docs to match. Use when a release has grown too complex to finish or polish everything, and the team needs to cut scope deliberately instead of drifting.
to-issues
Breaks a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when the user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
plan-review
Deep plan review with Pharaoh reconnaissance, wiring verification, and structured issue tracking. Use before implementing any feature, refactor, or significant code change. Enters plan mode (no code changes) and provides structured review with decision points.
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.