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/greglas75/zuvonpx agentmods add skills/greglas75/zuvo/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/greglas75/zuvo/backlog)<a href="https://agentmods.dev/skills/greglas75/zuvo/backlog"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/backlog/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/greglas75/zuvo/backlog"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 40 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 158 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00114 | $0.05933 |
| Opus 5.5 | $0.00046 | $0.02373 |
| Sonnet 5.5 | $0.00023 | $0.01187 |
| Haiku 4.5 | $0.00011 | $0.00593 |
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 yesterday.
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 — 481 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, resolved per ../../shared/includes/backlog-protocol.md ("Where the Backlog Lives"): when git tracks it in the checkout you are in, that checkout's copy is the backlog for its branch; otherwise it lives at the MAIN checkout root. The helper applies the rule — ~/.zuvo/backlog-archive.py path --repo "$PWD" prints the path — and every helper call below takes --repo "$PWD". By hand, copy the protocol's whole resolution block (its fallback is mandatory: without it a non-git CWD yields an empty root and re-forks the backlog).
For an UNTRACKED backlog, NEVER create or write a memory/backlog.md inside a linked worktree — one backlog per repository. If memory/ does not exist at the resolved root, create it. If the file does not exist, create it from the template at the bottom of this skill. If a legacy untracked worktree-local copy exists, merge its unique entries (by the dedup key defined in ../../shared/includes/backlog-protocol.md) 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 |
archive [--dry-run] |
Move ticked, resolution-marked entries to memory/backlog-done.md |
regression B-{N} |
Re-open an archived entry under the same id (lookup said ARCHIVED) |
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 |
verify |
Decide whether every entry is still TRUE, before anything is closed, ranked, grouped or rendered — see Mode: verify |
groom [--dry-run] |
Apply the dispositions those verdicts license; refuses on partial verification — see Mode: groom |
doc [--partial] |
Render the groomed working document under zuvo/reports/ — see Mode: doc |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +3 lines e309b3d357c8
- 7d ago Changed · -5 lines 6587c6fcf489
- 12d ago Changed · +127 lines · +29 tokens per session c6a551b44b9a
- 25d ago Changed · +7 lines ae9effdf3a30
- 28d ago Changed · +16 lines dfd84f6117fa
- 1mo ago First seen · 333 lines · 85 tokens per session scan A 2b4a35f1dbc9
backlog is a skill published in the GitHub repository greglas75/zuvo (8 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 5,933 once invoked, about $0.0005 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
ring:dispatching-workflows
Executing a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
ring:managing-dev-cycle
Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…
ring:planning-small-features
Planning the lightweight 4-gate Small Track pre-dev workflow (research, PRD, TRD, plan) with human approval and state tracking at each gate. Use for features under 2 days that reuse existing patterns and add no new dependencies, data models, or services. Skip for larger or complex features — use…