daily-summary

daily-summary is a skill for Claude Code, Codex from bettyguo/obsidian_mcp. It costs 28 tokens per session (612 once invoked), scanned A, original, MIT.

A note-taking workflow that reads recent daily notes and drafts a linked summary of their main themes. Daily notes are dated notes used to record activity over time.

In plain words
What is it for?
Use it for weekly reviews, synthesizing a chosen number of days, or finding ideas and related notes worth developing.
Why use it?
It helps someone returning after a gap see recurring topics and connections without rereading every recent note.

Skill for Claude CodeCodex

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

Good fit Use it for weekly reviews, synthesizing a chosen number of days, or finding ideas and related notes worth developing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bettyguo/obsidian_mcp/daily-summary
Install

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.

Any agent
npx skills add bettyguo/obsidian_mcp --skill daily-summary
Clone the repo
git clone --depth 1 https://github.com/bettyguo/obsidian_mcp

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-summary

README.md
[![agentmods](https://agentmods.dev/badge/skills/bettyguo/obsidian_mcp/daily-summary/github.svg)](https://agentmods.dev/skills/bettyguo/obsidian_mcp/daily-summary)
Your own site
<a href="https://agentmods.dev/skills/bettyguo/obsidian_mcp/daily-summary"><img src="https://agentmods.dev/badge/skills/bettyguo/obsidian_mcp/daily-summary/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-summary

Your own site · 80×15
<a href="https://agentmods.dev/skills/bettyguo/obsidian_mcp/daily-summary"><img src="https://agentmods.dev/badge/skills/bettyguo/obsidian_mcp/daily-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 612 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.00028 $0.00612
Opus 5 $0.00014 $0.00306
Sonnet 5 $0.00006 $0.00122
Haiku 4.5 $0.00003 $0.00061

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

Security

Grade A, and why

daily-summary 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 11d 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.

skills/daily-summary/SKILL.md · 53 lines

How it starts

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

When to use

The user wants a synthesis of recent daily-note activity — usually because they're returning to the vault after a gap, preparing a weekly review, or hunting for ideas worth expanding. The horizon defaults to 7 days; the user may specify (/daily-summary 30d).

Procedure

  1. Call vault_info to confirm the vault is accessible and to learn the daily-note pattern.
  2. Call list_daily_notes(since="7d") (or the user-specified horizon). If fewer than 3 daily notes returned, tell the user and stop — there's nothing to synthesize.
  3. Call read_notes_batch(paths=[...returned paths]) with the daily-note paths. Respect the 200K-char cap.
  4. Identify themes. Aim for 3–7 named threads, each with a one-sentence claim and 2–4 supporting daily-note references.
  5. For each theme, pick 1–2 wikilinks from the daily notes that look central. Use find_related if a theme would benefit from atomic-note context.
  6. Draft a synthesis note. Path: Syntheses/Daily summary {YYYY-MM-DD to YYYY-MM-DD}.md. Frontmatter: created: <today>, tags: [synthesis, daily-summary], period_start, period_end. Body uses the template in §Output format.
  7. Surface the proposed body to the user IN CHAT. Wait for approval (or --unattended).
  8. After approval, call create_note(path=..., body=..., frontmatter=..., confirm=true).
  9. Reply with the new path and a 2-sentence top-line.

Output format

# Daily summary, {YYYY-MM-DD} to {YYYY-MM-DD}

## Threads

### {Theme 1 — short imperative sentence}
{One paragraph of synthesis, referencing daily notes with wikilinks.}
- [[Daily Notes/YYYY-MM-DD]]: {short pull-quote or paraphrase}
- ...

### {Theme 2 ...}

## Loose ends
- {Question I left unresolved} — see [[Daily Notes/YYYY-MM-DD]]

## Sources
- [[Daily Notes/YYYY-MM-DD]] ... (every daily note read, in chronological order)

Anti-patterns

  • Don't summarize line-by-line. Surface threads, not transcripts.
  • Don't invent themes the daily notes don't actually contain. If the period is sparse, say so.
  • Don't edit the source daily notes — read-only.
  • Don't run more than one find_related per theme. The synthesis is from what the user already wrote, not from new search.

Read the full file on GitHub · 53 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. 11d ago First seen · 53 lines · 28 tokens per session scan A 07eb8829b4bc

Subscribe to this mod's changes

daily-summary is a skill published in the GitHub repository bettyguo/obsidian_mcp (8 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 612 once invoked, about $0.0001 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

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

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

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens