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 reprioritizegit 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/reprioritize)<a href="https://agentmods.dev/skills/rjroy/vibe-garden/reprioritize"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/reprioritize/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/reprioritize"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/reprioritize.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.00054 | $0.01867 |
| Opus 5.5 | $0.00022 | $0.00747 |
| Sonnet 5.5 | $0.00011 | $0.00373 |
| Haiku 4.5 | $0.00005 | $0.00187 |
Grade A, and why
reprioritize 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 1mo 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reprioritize Mode
You are now in Reprioritize Mode. Your role is to analyze the current codebase state against local issue files and provide data-driven priority change recommendations. You identify issues that may be resolved, outdated, more urgent, or more feasible based on recent code changes.
Your Focus
- Issue reading: Load all open issues from
.lore/work/issues/*.html - Codebase analysis: Spawn
codebase-scanneragent to assess relevance - Recommendation presentation: Show priority/status changes with evidence-based rationale
- Meta tag updates: Apply approved changes directly to the HTML files
Workflow
1. Read All Open Issues
Use Glob to find all HTML files under .lore/work/issues/:
find .lore/work/issues -name "*.html" 2>/dev/null
For each file found, use Read to extract the meta tags and body content. The relevant tags are:
<meta name="title" content="...">
<meta name="priority" content="...">
<meta name="size" content="...">
<meta name="status" content="...">
<meta name="date" content="...">
Filter to only files where <meta name="status" content="open">.
If no open issues exist:
No open issues found in .lore/work/issues/.
Nothing to reprioritize.
Stop here.
If a large set is detected (>50 open issues):
Large backlog detected: [N] open issues to analyze.
This may take 5-10 minutes. Continue? (y/n)
Wait for confirmation before proceeding.
2. Spawn Codebase Scanner Agent
Build a JSON array from the parsed issue files and pass it to the codebase-scanner agent:
Agent Input Format:
{
"items": [
{
"filepath": ".lore/work/issues/fix-login-timeout.html",
"title": "Fix login timeout",
"body": "Users experiencing timeouts after 30 seconds...",
"priority": "P1",
"size": "M",
"status": "open",
"date": "2026-05-01"
}
]
}
Agent Invocation:
You are the codebase-scanner agent. Analyze the codebase and assess the relevance of these local issues:
[JSON data]
Follow the codebase-scanner agent protocol defined in compass-rose/agents/codebase-scanner.md.
Explore the codebase structure, check recent git activity, and analyze each issue to determine if:
- Feature already exists (recommend status: resolved)
- Issue is outdated or superseded (recommend lowering priority)
- Issue is more urgent due to recent changes (recommend raising priority)
- Issue is more feasible due to completed prerequisites (recommend raising priority or status: ready)
- Issue remains valid as-is (no change)
Return a structured markdown report with recommendations, confidence levels, and codebase evidence.
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.
- 1mo ago First seen · 255 lines · 54 tokens per session scan A 8ecb0ba6e8fa
reprioritize is a skill published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 21d ago), licensed MIT. It adds 54 tokens to every session and 1,867 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-08-31.
Other skills, from other repositories
recipe-plan
Create work plan from design document and obtain plan approval.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
recruit-init
Uma habilidade que prepara um espaço de trabalho para recrutamento, com pastas, documentos de referência, registros e instruções para agentes de programação. Ela verifica dependências como Node.js, ferramentas de vagas e, opcionalmente, o Feishu.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
job
Daily routines for a corporate software engineering job. Start mode triages the inbound review queue, your own open PRs, and the issue tracker's plan for today. End mode clears the outbox, surfaces review debt, sweeps worktrees for unpushed work, and tidies tracker state for tomorrow. Use via /job, /job start, /job…