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 bettyguo/obsidian_mcp --skill daily-summarygit clone --depth 1 https://github.com/bettyguo/obsidian_mcpWrote 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/bettyguo/obsidian_mcp/daily-summary)<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.
<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>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.00028 | $0.00612 |
| Opus 5.5 | $0.00011 | $0.00245 |
| Sonnet 5.5 | $0.00006 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
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 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 — 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
- Call
vault_infoto confirm the vault is accessible and to learn the daily-note pattern. - 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. - Call
read_notes_batch(paths=[...returned paths])with the daily-note paths. Respect the 200K-char cap. - Identify themes. Aim for 3–7 named threads, each with a one-sentence claim and 2–4 supporting daily-note references.
- For each theme, pick 1–2 wikilinks from the daily notes that look central. Use
find_relatedif a theme would benefit from atomic-note context. - 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. - Surface the proposed body to the user IN CHAT. Wait for approval (or
--unattended). - After approval, call
create_note(path=..., body=..., frontmatter=..., confirm=true). - 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_relatedper theme. The synthesis is from what the user already wrote, not from new search.
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 · 53 lines · 28 tokens per session scan A 07eb8829b4bc
daily-summary is a skill published in the GitHub repository bettyguo/obsidian_mcp (8 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 612 once invoked, about $0.0001 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
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.
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…