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/ovid/paad/backlognpx skills add Ovid/paad --skill backloggit clone --depth 1 https://github.com/Ovid/paadWrote 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/ovid/paad/backlog)<a href="https://agentmods.dev/skills/ovid/paad/backlog"><img src="https://agentmods.dev/badge/skills/ovid/paad/backlog.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 | $0.00073 | $0.03165 |
| Opus 5 | $0.00036 | $0.01582 |
| Sonnet 5 | $0.00015 | $0.00633 |
| Haiku 4.5 | $0.00007 | $0.00316 |
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 3d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
On invocation: announce "Running paad:backlog v1.31.0-preview", then immediately proceed with the steps below — do not stop after announcing.
Backlog
Experimental. Arguments, modes, and behavior may change — or this skill may be withdrawn — in any release, including a patch release. The semver promise the settled skills carry does not apply here. If you build a workflow on it, pin your plugin version and file what breaks.
Work the project-wide bug backlog at paad/code-reviews/backlog.md — the file /agentic-review writes its out-of-scope findings to. Two modes: Clean re-verifies every entry against the current code and drops the ones already fixed or gone; Fix picks the next entry and fixes it end-to-end. This is the always-available entry point into that backlog.
This is a technique skill. Follow the mode's steps in order. Two rules bind both modes and are the reason the skill exists:
- This skill never runs
git commit. It edits files and prints the commit command for the user to run — matching/agentic-review, which writes files and leaves committing to the user. Removing a backlog entry destroys a record; the user decides when that record change is committed and with what message. Printing the command is the deliverable, not an afterthought. - A backlog entry is deleted only on evidence read from the current code — never on doubt, and never on the skill's own say-so that it fixed something. An entry wrongly kept costs one line; an entry wrongly deleted silently loses a real bug.
Flow:
digraph backlog {
"Invoked" [shape=doublecircle];
"Backlog missing or empty?" [shape=diamond];
"STOP: report empty, suggest /agentic-review" [shape=box, style=bold];
"Mode from $ARGUMENTS?" [shape=diamond];
"List entries; show menu; WAIT for choice" [shape=box];
"CLEAN: one skeptical read-only analyst per entry" [shape=box];
"Verdict, decided from code at the cited lines?" [shape=diamond];
"Any doubt: KEEP the entry (never delete on ambiguity)" [shape=box, style=bold];
"Delete RESOLVED/GONE entries + merge-losers" [shape=box];
"FIX: rank by severity then age; propose top; WAIT for pick" [shape=box];
"Fix the bug (directly or via /vibe)" [shape=box];
"Independent read-only analyst reads code; best-effort tests (none: inspection only, never a pass alone)" [shape=box];
"Analyst confirms the specific bug is gone?" [shape=diamond];
"KEEP entry; report what is still wrong" [shape=box, style=bold];
"Delete the entry" [shape=box];
"Print the git commit command for the user; NEVER run git commit" [shape=box, style=bold];
"Done" [shape=doublecircle];
"Invoked" -> "Backlog missing or empty?";
"Backlog missing or empty?" -> "STOP: report empty, suggest /agentic-review" [label="yes"];
"Backlog missing or empty?" -> "Mode from $ARGUMENTS?" [label="no"];
"Mode from $ARGUMENTS?" -> "List entries; show menu; WAIT for choice" [label="none"];
"Mode from $ARGUMENTS?" -> "CLEAN: one skeptical read-only analyst per entry" [label="clean"];
"Mode from $ARGUMENTS?" -> "FIX: rank by severity then age; propose top; WAIT for pick" [label="fix"];
"List entries; show menu; WAIT for choice" -> "CLEAN: one skeptical read-only analyst per entry" [label="1 clean"];
"List entries; show menu; WAIT for choice" -> "FIX: rank by severity then age; propose top; WAIT for pick" [label="2 fix"];
"CLEAN: one skeptical read-only analyst per entry" -> "Verdict, decided from code at the cited lines?";
"Verdict, decided from code at the cited lines?" -> "Any doubt: KEEP the entry (never delete on ambiguity)" [label="STILL-PRESENT / unsure"];
"Verdict, decided from code at the cited lines?" -> "Delete RESOLVED/GONE entries + merge-losers" [label="RESOLVED / GONE, cited"];
"Any doubt: KEEP the entry (never delete on ambiguity)" -> "Print the git commit command for the user; NEVER run git commit";
"Delete RESOLVED/GONE entries + merge-losers" -> "Print the git commit command for the user; NEVER run git commit";
"FIX: rank by severity then age; propose top; WAIT for pick" -> "Fix the bug (directly or via /vibe)";
"Fix the bug (directly or via /vibe)" -> "Independent read-only analyst reads code; best-effort tests (none: inspection only, never a pass alone)";
"Independent read-only analyst reads code; best-effort tests (none: inspection only, never a pass alone)" -> "Analyst confirms the specific bug is gone?";
"Analyst confirms the specific bug is gone?" -> "Delete the entry" [label="yes"];
"Analyst confirms the specific bug is gone?" -> "KEEP entry; report what is still wrong" [label="no"];
"Delete the entry" -> "Print the git commit command for the user; NEVER run git commit";
"KEEP entry; report what is still wrong" -> "Done";
"Print the git commit command for the user; NEVER run git commit" -> "Done";
}
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.
- 3d ago First seen · 177 lines · 73 tokens per session scan A 469e33cfd3bd
backlog is a skill published in the GitHub repository Ovid/paad (105 stars, last pushed 4d ago), licensed MIT. It adds 73 tokens to every session and 3,165 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-30.
Other skills, from other repositories
nopua
The anti-PUA. Drives AI with wisdom, trust, and inner motivation instead of fear and threats. Activates on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '换个方法', '为什么还不行').…
nopua-lite
NoPUA Lite — core wisdom in 1.5k tokens. Drives AI with trust and inner motivation instead of fear. Same Daoist philosophy, minimal footprint. For personal use and small-context models.
ccg-annotate
AI-driven annotation workflow for adding structured metadata to code. Annotations are indexed and searchable via FTS.
ccg-namespace
Isolate read-only CCG search, documentation discovery, and analysis by namespace. Use when working across multiple repositories or services, preventing cross-project graph leakage, federating supported reads, or traversing materialized cross-namespace references. Do not use for graph writes or scoped updates; the user…
ccg-docs
Generate Markdown documentation from code graphs, build RAG indexes for AI consumption, and lint documentation quality.
ccg-analyze
Explicit-only deep analysis of algorithms, feature pipelines, and code relationships with CCG impact radius, bounded flow tracing, callers/callees, git-diff risk, affected stored flows, and cross-namespace references. Use only when the user explicitly names the ccg-analyze skill in the current request. Do not invoke…