logseq-daily-summary

logseq-daily-summary is a skill for Codex from Shitao5/my_skills. It costs 51 tokens per session (797 once invoked), scanned A, original, MIT.

A tool for summarizing a LogSeq daily journal, where LogSeq is a note-taking app that stores linked pages and dated journal entries. It writes a summary of up to 300 Chinese characters back into the selected journal page.

In plain words
What is it for?
Use it to summarize today’s journal or a specified date, review the page’s contents, and append the concise result to LogSeq.
Why use it?
It turns a day’s notes into a short record while keeping the summary in the same journal entry and including the day’s Codex CLI usage statistics.

Skill for Codex

Written for Codex: reads ~/.codex or $CODEX_HOME. Also seen: mentions Codex.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/wushitao/.codex/skills/logseq-daily-summary/scripts/codex_usage_stats.py.

Good fit Use it to summarize today’s journal or a specified date, review the page’s contents, and append the concise result to LogSeq.

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: 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 logseq-daily-summary

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/shitao5/my_skills/logseq-daily-summary"><img src="https://agentmods.dev/badge/skills/shitao5/my_skills/logseq-daily-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 797 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.00051 $0.00797
Opus 5 $0.00026 $0.00398
Sonnet 5 $0.00010 $0.00159
Haiku 4.5 $0.00005 $0.00080

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

Security

Grade A, and why

logseq-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 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/codex_usage_stats.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

logseq-daily-summary/SKILL.md · 58 lines

How it starts

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

Logseq Daily Summary

Overview

Summarize a LogSeq daily journal (today by default, or a specified log) and append a concise <=300 Chinese-character paragraph back into that day’s journal page.

Workflow (LogSeq journal -> usage stats -> summary -> write back)

  1. Determine the target journal page.
  • If the user specifies a log/date/page name, use that.
  • Otherwise use today’s date based on local time. Use list_pages (include journals) and find a page whose title starts with YYYY-MM-DD. LogSeq journal titles may be YYYY-MM-DD DayName (English), YYYY-MM-DD 星期X (Chinese), or just YYYY-MM-DD.
  • If multiple pages match, prefer the one marked [journal], then the one with the longest non-empty content (via get_page_content), then the English weekday variant.
  • If no page matches the date, use search to confirm. If still missing, ask the user for the exact page name before creating a new page.
  1. Read the journal content.
  • Use get_page_content to fetch the page content.
  • If the page does not exist, create it (via create_page or update_page) and note it was empty before summarizing.
  1. Collect today's Codex CLI usage stats and append a usage block.
  • Use the fixed script: scripts/codex_usage_stats.py.
  • Example: python3 /Users/wushitao/.codex/skills/logseq-daily-summary/scripts/codex_usage_stats.py --date YYYY-MM-DD.
  • The script reads ~/.codex/sessions/YYYY/MM/DD/*.jsonl, aggregates the last token_count.total_token_usage per session file, and extracts the local time range for the day (min/max timestamps).
  • Append the script output as its own LogSeq block before the summary block, using the exact format below (no leading "- "):
🤖 Codex CLI 消耗(自动统计)
  ⏱️ 时间段: YYYY-MM-DD HH:MM:SS–HH:MM:SS (+0800)
  🧾 用量: N tokens
  🧠 Token: 输入 A / 输出 B / 缓存输入 C / 推理 D
  1. Write the summary.
  • Produce a single paragraph in Chinese, 300 characters or fewer (do not count the usage block).
  • Focus on “what I was thinking about / investigating today,” derived from the journal content.
  • Avoid lists in the summary paragraph; keep it clean and readable.

Read the full file on GitHub · 58 lines

Files

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.

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 · 58 lines · 51 tokens per session scan A c949fb990075

Subscribe to this mod's changes

logseq-daily-summary is a skill published in the GitHub repository Shitao5/my_skills (5 stars, last pushed 8mo ago), licensed MIT. It adds 51 tokens to every session and 797 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