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/vincentmumme/personalos-boilerplatenpx agentmods add skills/vincentmumme/personalos-boilerplate/priority-dashboardWrote 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/vincentmumme/personalos-boilerplate/priority-dashboard)<a href="https://agentmods.dev/skills/vincentmumme/personalos-boilerplate/priority-dashboard"><img src="https://agentmods.dev/badge/skills/vincentmumme/personalos-boilerplate/priority-dashboard/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/vincentmumme/personalos-boilerplate/priority-dashboard"><img src="https://agentmods.dev/badge/skills/vincentmumme/personalos-boilerplate/priority-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.01235 |
| Opus 5 | $0.00030 | $0.00617 |
| Sonnet 5 | $0.00012 | $0.00247 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
priority-dashboard 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 12d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: priority-dashboard
Contract
This skill produces exactly one current read model at priority dashboard. It reads canonical Actions, due Attention Triggers, relevant linked owner state, and the optional temporary priority control. It never owns task text, deadlines, evidence, completion, lifecycle, project truth, or recurring commitments.
The dashboard contains no checkboxes and no independent completion controls. Every surfaced item links to its canonical Action or Trigger and states why it is prioritized. The bounded view contains exactly one current focus, at most three next-seven-day outcomes, and enough 30-day life gates to keep the combined main-focus set at no more than five Actions. Waiting/cashflow risk and stale review remain separate lanes. Routine receipt/Admin work is invisible outside the final five calendar days and then appears only as a month-end batch; payment and material risk exceptions stay in the risk lanes.
Ranking follows [[system/frameworks/operations/priority-dashboard]]: effective {{user_name}} control first, then real due deadlines inside a rolling seven-day horizon, explicit critical/high priority and actual in-progress work, linked owner impact, soft target tie-breaking, and finally opportunities. A target never creates focus by itself. Free-text cadence words never affect rank. An expired control is ignored automatically and remains visibly identified as expired.
Rebuild
Run from the PersonalOS root:
python3 skills/priority-dashboard/scripts/rebuild.py --reason manual
Use the explicit reason matching the event:
python3 skills/priority-dashboard/scripts/rebuild.py --reason manual-priority-change
python3 skills/priority-dashboard/scripts/rebuild.py --reason operational-state-change
The scheduled VPS run uses --reason scheduled --timezone Europe/Berlin. The timezone argument is explicit scheduler context, not a duplicate hidden default.
Steering
When {{user_name}} changes focus, ordering, or exclusions:
What ships with it
3 files 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.
- 12d ago First seen · 100 lines · 60 tokens per session scan A 5e79f4fd0c6e
priority-dashboard is a skill published in the GitHub repository vincentmumme/personalos-boilerplate (19 stars, last pushed 17d ago), licensed MIT. It adds 60 tokens to every session and 1,235 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
wrap-session-up
End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.
gws-obsidian-prep
Cross-skill recipe: fetch today's (or tomorrow's) Google Calendar events via gws CLI and create meeting prep notes in the Obsidian vault.
obsidian
Obsidian vault management — create notes, backlinks, tags, and Dataview queries via file operations.
resume
A workflow for reopening a paused task by scanning its saved project notes, blockers, logs, and delegated work. It presents the parked tasks so the user can choose which one to continue.
vault-onboarding-guide
An interactive guide for learning a file-based knowledge store with an agent. It teaches how to organize incoming material, projects, plans, tasks, logs, parked work, and resumed work.
weekly
Run the weekly review of the big-brain second brain: triage the inbox, walk active projects, reschedule or drop overdue tasks, check vault health, and write a review summary. Use when the user types /weekly, or asks for a "weekly review", "review my projects", "clean up my brain", "triage my inbox".