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 skills add kensaurus/cursor-kenji --skill housekeep-backloggit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/housekeep-backlog)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/housekeep-backlog"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/housekeep-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/kensaurus/cursor-kenji/housekeep-backlog"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/housekeep-backlog.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.00062 | $0.01811 |
| Opus 5.5 | $0.00025 | $0.00724 |
| Sonnet 5.5 | $0.00012 | $0.00362 |
| Haiku 4.5 | $0.00006 | $0.00181 |
Grade A, and why
housekeep-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 29d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
housekeep-backlog — Living register of parked work
Degree of freedom: MIXED. Discovery scan [LOW freedom — run exactly].
Classification, dedup, priority [HIGH freedom].
Apply-now for the register only. You do not implement backlog items
here. Every plan-* skill creates parked work; this is the collector.
The failure mode is not making the inventory — it goes stale within a
month and nobody can tell if debt is shrinking. So this is docs-adr
for parked work: regenerate, diff against the last run, keep stable IDs.
Prefer docs/BACKLOG.md. Use a root BACKLOG.md only if the host already
has one.
This skill vs neighbors
| Skill | Owns |
|---|---|
| housekeep-backlog (this) | Discover + dedup + write/diff the register |
complete-everything |
Execute one approved plan to closure |
burndown-full |
Drive one mechanical change to 100% |
docs-adr |
Decision memory, not parked-work inventory |
plan-stub-checker |
Stub/dead-UI plan (feeds this register) |
workflow-feature-flag |
Flag debt execution |
workflow-housekeep |
README / dead files / deps — not the backlog |
workflow-release-prep |
What's done in the dirty tree → merge-ready PR |
enhance-agent-guardrails |
Installs the same-PR / "read BACKLOG.md" wording |
How to reason (every candidate)
- Locate — file:line or doc path; form (TODO / parked phase / skip / open finding / flag)
- Interpret — what actual work is it? A bare
// TODO: fixis itself a finding — tagneeds-triage, do not drop it - Classify — tech-debt / unfinished-feature / deferred-plan-phase / test-gap / known-bug / decision-needed
- Status — still-relevant / verify-done / stale-or-obsolete
Skipping Interpret produces a register of context-free TODOs nobody can action.
Worked example
Locate:
docs/plans/auth-refactor.md— phases 1–2 checked, 3–4 unchecked; last commit 4 months ago. Interpret: phase 3 is refresh-token rotation; phase 4 is audit follow-ups parked mid-plan. Classify: deferred-plan-phase (two items). Status: ph3 still-relevant; ph4 —audit-auth-flowshas since run, so verify-done before carrying it. Rows:BL-014 | deferred-phase | auth-refactor ph3: refresh rotation | relevant | high | docs/plans/auth-refactor.mdBL-015 | deferred-phase | auth-refactor ph4: audit follow-ups | verify-done | med | docs/plans/auth-refactor.md
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.
- 29d ago Changed · +1 lines · -15 tokens per session b4811b6f2046
- 1mo ago First seen · 149 lines · 77 tokens per session scan A 916963fdd3d4
housekeep-backlog is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 24d ago), licensed MIT. It adds 62 tokens to every session and 1,811 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-09-03.
Other skills, from other repositories
noteplan
Read, search, create, and edit NotePlan notes and daily logs directly via the filesystem. Use this skill whenever the user references NotePlan, daily notes, weekly notes, project notes, or wants to check/update their planning. Triggers: 'noteplan', 'daily note', 'today's note', 'weekly note', 'check my notes', 'add to…
lno-task-prioritization
Classify tasks as Leverage, Neutral, or Overhead using Shreyas Doshi's LNO framework to maximize impact and reduce stress. Use when the user is planning their week, feeling overwhelmed, prioritizing a to-do list, doing sprint planning, or asking how to spend their time more effectively.
pre-mortem-facilitator
Facilitate a pre-mortem session using Shreyas Doshi's Tigers/Paper Tigers/Elephants framework. Use when the user is planning a launch, starting a critical project, preparing for a major initiative, or wants to proactively identify risks before something goes wrong.
task
Use when creating, updating, or managing task files for projects and plans.
dynamic-context
Use when managing context window to optimize token usage and prevent context bloat.
prismer-apple-reminders
Apple Reminders via remindctl: add, list, complete.