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 davekilleen/Dex --skill daily-reviewgit clone --depth 1 https://github.com/davekilleen/DexWrote 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/davekilleen/dex/daily-review)<a href="https://agentmods.dev/skills/davekilleen/dex/daily-review"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/daily-review/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/davekilleen/dex/daily-review"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/daily-review.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.00072 | $0.04955 |
| Opus 5.5 | $0.00029 | $0.01982 |
| Sonnet 5.5 | $0.00014 | $0.00991 |
| Haiku 4.5 | $0.00007 | $0.00496 |
Grade A, and why
daily-review 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 today.
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 — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Conduct an end-of-day review to capture progress, track what you actually accomplished vs. planned, surface meeting follow-ups, and set up tomorrow.
Execution mode
Run inline in the current conversation by default. Do not fork merely because this skill was selected. Only run in the background when the user explicitly asks for a background review or the host has already obtained a specific background-work approval for this review.
Before authoring anything, check for existing day state: today's archived plan, today's completion metrics, and any review or closeout already written for today. If existing day state is present, enter verifier mode. Read it, compare it with the current tasks and meeting evidence, and surface omissions or proposed corrections. Do not create a competing review or overwrite the existing author. Any proposed write still follows the confirmation and write-guard rules below.
Delegated gathering (large-vault scaling)
This skill stays inline as described above: it keeps session awareness, it asks the user the questions, and it owns every interactive step. What it does NOT do inline is the bulk read-gathering, which on a mature vault (hundreds of notes, thousands of indexed messages, a live calendar and multiple integrations) can be large enough to exhaust the main conversation before the useful work starts.
So the gathering phase is delegated to one general-purpose subagent via the
Agent tool, using the self-contained prompt in this skill's
AGENT_INSTRUCTIONS.md:
- Read
.agents/skills/daily-review/AGENT_INSTRUCTIONS.md. - Substitute its placeholders (
{{TARGET_DATE}},{{TOMORROW_DATE}},{{TOMORROW_DATE_PLUS_1}},{{DAY_NAME}},{{MONTH}},{{DD}},{{YYYY}}). - Call the Agent tool with
subagent_type: "general-purpose",model: "sonnet", that prompt, and a short description. The brief is mechanical gathering, so it runs on the fast tier; the judgement calls stay in this conversation on the default model. - Verify it wrote the draft to
07-Archives/Reviews/Daily_Review_YYYY-MM-DD.md, then run the interactive steps from its findings and complete the placeholder sections.
What ships with it
1 file 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.
- today Changed bfb391730c16
- 26d ago Changed b90b500c3732
- 29d ago Changed · +4 lines 595b09185284
- 1mo ago Changed 5371031a9b43
- 1mo ago Changed · +9 lines fa6251e8bf0f
- 1mo ago First seen · 558 lines · 72 tokens per session scan A 0a332b12945e
daily-review is a skill published in the GitHub repository davekilleen/Dex (508 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 4,955 once invoked, about $0.0003 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-02.
Other skills, from other repositories
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
meeting-notes
Use when the user asks to capture, structure, or summarize meeting notes / call notes / 1:1 discussion / standup notes. Produces a standard template with attendees, agenda, decisions, action items (owner + deadline), and open questions.
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).
inbox-management
Ongoing Gmail inbox management via scheduled runs. Archives known noise, flags urgent items, drafts replies in-thread (never auto-sends), and catches stale follow-ups. Empty polls spend no model tokens. Starts in flag-only mode.
inbox-cleanup
Run a high-recall, multi-pass email inbox cleanup. Pattern-based subject queries catch 25x more archivable email than sender scans alone. Includes urgency triage, classification signals, and post-cleanup filter setup.
notifications
Send notifications through the unified notification router.