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 rjroy/vibe-garden --skill next-itemgit clone --depth 1 https://github.com/rjroy/vibe-gardenWrote 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/rjroy/vibe-garden/next-item)<a href="https://agentmods.dev/skills/rjroy/vibe-garden/next-item"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/next-item/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/rjroy/vibe-garden/next-item"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/next-item.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.00052 | $0.00742 |
| Opus 5 | $0.00026 | $0.00371 |
| Sonnet 5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
next-item 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 10d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Item Recommendation
You are in Next Item Recommendation mode. Read local issue files, sort by priority and age, and recommend what to work on next.
Workflow
1. Find Open Issues
Use Glob to find all issue files:
.lore/work/issues/*.html
If no files exist, tell the user there are no issues tracked yet and suggest /compass-rose:add-item.
2. Extract Metadata
For each file, extract the following meta tags and the page title. The most efficient approach is a single grep pass:
grep -h 'name="status"\|name="priority"\|name="size"\|name="date"\|<title>' .lore/work/issues/*.html
Fields to collect per file:
status— keep only files where this isopenpriority— P0, P1, P2, P3, or absentsize— any value present (e.g. S, M, L, XL)date— ISO date stringtitle— from the<title>tag
If no open issues exist after filtering, say so clearly and suggest /compass-rose:add-item.
3. Sort
Sort the open issues by:
- Priority (primary): P0 first, then P1, P2, P3, unprioritized last
- Date (tiebreaker): ascending — oldest issue first
4. Present Top Items
Display the top 2–3 as a table:
| # | Title | Priority | Size | Date |
|---|------------------------------|----------|------|------------|
| 1 | Fix session expiry handling | P0 | S | 2026-03-12 |
| 2 | Add export to CSV | P1 | M | 2026-02-28 |
| 3 | Improve error messages | P1 | S | 2026-04-01 |
Follow with a recommendation paragraph: name the top item, its priority, and a plain-language rationale for why it ranks first (priority level, age, or both if relevant).
If two items tie on priority, note that date broke the tie.
5. Edge Cases
No open issues: State that clearly. Suggest /compass-rose:add-item to create the first one.
Missing priority on some items: Treat them as lower than P3. Mention in the output that some items have no priority set.
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.
- 10d ago First seen · 83 lines · 52 tokens per session scan A 2496b30758e9
next-item is a skill published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 742 once invoked, about $0.0003 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
init-rpm
Project setup and verification. First run creates rpm context for a project. Repeat runs verify that an existing rpm setup matches the latest expected layout and apply safe migrations.
backlog
Manage the rpm backlog (long-term project tasks in docs/rpm/future/tasks.org — distinct from Claude's native TaskCreate list, which is session-scoped). Add, list, review, postpone, or complete entries. TRIGGER on natural-language backlog operations — phrasings like "backlog X", "add X to backlog", "add to backlog"…
version
Report the installed rpm plugin version. Use when the user asks for the rpm version, plugin version, installed version, or wants to verify which rpm release is loaded.
recursive-spine-digest
Use when sweeping all recursive-spine-conforming repos for tracking health — aging deferrals (oldest first), stalled milestones, in-flight by lane, assigned-but-untouched issues, and debts named in closing comments but never filed, plus seedling pollen that never transplanted (hive repos). Reports honest denominators…
recursive-spine-scaffold
Use when a repo has (or is getting) the tracking stamp and needs the rest of its spine — interviews for and stamps up to six parts, each optional: a rules codex with a moments map, an ADR directory, a CI gate skeleton, a session-memory convention, a constraints file with its sha-pinned drift gate, and the loop…
recursive-spine-nudge
Use after a recursive-spine-digest sweep to select and deliver system-initiated nudges — 0–3 conversation-starters pushed to the owner about what is unblocked, aging, stalled, or newly connected. Every nudge ends in a question; the skill proposes conversations, never executes work.