daily-note-review

daily-note-review is a skill for Claude Code, Codex from zazencodes/zazencodes-obsidian-agent-course. It costs 65 tokens per session (851 once invoked), scanned A, original, MIT.

A review workflow for unprocessed daily notes in an Obsidian vault, which is a folder of linked notes managed by Obsidian.

In plain words
What is it for?
Use it to route daily-note items into project or area notes, mark them processed, and summarize what was filed or needs a decision.
Why use it?
It prevents useful tasks, references, and ideas from remaining buried in daily notes and avoids processing notes that were already reviewed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/you/obsidian/YourVault.

Good fit Use it to route daily-note items into project or area notes, mark them processed, and summarize what was filed or needs a decision.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for daily-note-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/zazencodes/zazencodes-obsidian-agent-course/daily-note-review/github.svg)](https://agentmods.dev/skills/zazencodes/zazencodes-obsidian-agent-course/daily-note-review)
Your own site
<a href="https://agentmods.dev/skills/zazencodes/zazencodes-obsidian-agent-course/daily-note-review"><img src="https://agentmods.dev/badge/skills/zazencodes/zazencodes-obsidian-agent-course/daily-note-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.

agentmods 80×15 button for daily-note-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/zazencodes/zazencodes-obsidian-agent-course/daily-note-review"><img src="https://agentmods.dev/badge/skills/zazencodes/zazencodes-obsidian-agent-course/daily-note-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 851 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.00851
Opus 5 $0.00032 $0.00426
Sonnet 5 $0.00013 $0.00170
Haiku 4.5 $0.00006 $0.00085

Measured 12d ago against content hash 5c77895b11e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

daily-note-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 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.

resources/skills/daily-note-review/SKILL.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Daily Note Review

Vault root: /Users/you/obsidian/YourVault

Steps

  1. Find unprocessed notes — list all files in Daily/ and filter to those with review_status: unprocessed in their frontmatter.
  2. Read each note — use obsidian read path=Daily/YYYY-MM-DD.md.
  3. Triage content — route each item per the Triage Rules below.
  4. Mark as processed — set review_status: processed and reviewed_on: <today> on the note using obsidian property:set.
  5. Summarise — produce a bullet list: what was filed, what was left in place, any items flagged for the user to decide.

Process notes in chronological order (oldest first).

Finding Unprocessed Notes

grep -rl "review_status: unprocessed" /Users/you/obsidian/YourVault/Daily/

Triage Rules

Content type Action
Task tied to a named project Append to Projects/<project>/tasks/<relevant-task>.md, or create a new task note there
Task with no clear project Append as - [ ] item to the relevant Areas/<domain>/ note
Reference / link / resource Append to the relevant Areas/<domain>/ note
YouTube video idea or content angle Append to Projects/ZazenCodes/Video Board/ or create a task note
Business / strategy thought Append to Projects/ZazenCodes/Business Board/ or create a task note
Reflection or journal content Leave in place — do not move
Unclear / doesn't fit Leave in place and flag in the summary for the user

Default to leaving things in place and flagging. Do not create new top-level folders or restructure the vault without explicit user instruction.

Do not add frontmatter to notes you create. Write plain note bodies. Only add frontmatter when it's clearly required — e.g. you're adding an entry to a folder whose notes are all structured records with consistent properties (a database-like collection). When in doubt, leave it out.

Routing Map

Areas/
  Admin/            personal admin, accounts, paperwork
  Business/         business ideas outside ZazenCodes
  Culture/          books, film, art, recommendations
  Exercise/         fitness, training
  Family/
  Food & Drink/     recipes, restaurants
  Health & Body/    health, supplements, medical
  Investing/        finances
  Japanese Language/
  Mindfulness/      meditation, reflection, wellbeing
  Music/
  Network/          contacts, relationships
  Performance/      productivity, deep work
  Shop/             things to buy
  Skill/            skills to learn
  Social/
  Software/         dev tools, software notes
  Travel/

Projects/
  ZazenCodes/       YouTube channel, newsletter, courses, business
    Video Board/
    Business Board/
  Emanator/         AI / agent work

Read the full file on GitHub · 95 lines

Changes

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.

  1. 12d ago First seen · 95 lines · 65 tokens per session scan A 5c77895b11e0

Subscribe to this mod's changes

daily-note-review is a skill published in the GitHub repository zazencodes/zazencodes-obsidian-agent-course (6 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 851 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.

Related

Other skills, from other repositories

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

Migrate

Intakes external content, classifies chunks against LifeOS taxonomy, commits with provenance. Sources: .md/.txt, stdin, LifeOS dirs, CLAUDE.md/Cursor/OpenAI Custom Instructions, Obsidian/Notion/Apple Notes exports. MigrateScan classifies → routing table. MigrateApprove with…

danielmiessler/LifeOS · 158 tokens

daily-briefing

Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…

vellum-ai/vellum-assistant · 75 tokens

company-brain

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…

coreyhaines31/makerskills · 322 tokens

email-assistant

Read, search, draft, and send emails via Himalaya CLI or Python IMAP/SMTP. Requires email account configuration.

fuyuxiang/echo-agent · 29 tokens

calendar

Manage calendar events via CalDAV (Google/iCloud/Nextcloud) or local ICS files. View, create, and query events.

fuyuxiang/echo-agent · 29 tokens