logseq-wiki: Skill for Claude Code

.skills/wiki-digest/SKILL.md

wiki-digest is a skill for Claude Code, Codex from ystreibel/logseq-wiki. It costs 135 tokens per session (2,233 once invoked), scanned A, original, MIT.

A periodic summary of changes and new ideas in a Logseq wiki, a collection of linked Markdown notes. It can cover a day, week, month, or chosen date range.

In plain words
What is it for?
Use it to create daily, weekly, or monthly knowledge digests from the wiki. It highlights learned topics, updated notes, emerging themes, and items worth reviewing.
Why use it?
It turns scattered notes and updates into a readable review, making it easier to see what you learned and what needs revisiting.

Skill for Claude CodeCodex

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

This is ystreibel/logseq-wiki's own configuration. It tells Claude Code and Codex how to work on logseq-wiki itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything logseq-wiki configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ystreibel/logseq-wiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ystreibel/logseq-wiki/main/.skills/wiki-digest/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ystreibel/logseq-wiki

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 wiki-digest

README.md
[![agentmods](https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-digest.svg)](https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-digest)
Your own site
<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-digest"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-digest.svg" alt="Measured on agentmods" height="20"></a>
Per session 135 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,233 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.00135 $0.02233
Opus 5 $0.00068 $0.01117
Sonnet 5 $0.00027 $0.00447
Haiku 4.5 $0.00014 $0.00223

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

Security

Grade A, and why

wiki-digest 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 7d 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/wiki-digest/SKILL.md · 190 lines

How it starts

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

Wiki Digest — Générateur de Newsletter de Connaissance

Tu génères un digest lisible de l'activité récente du wiki : ce qui a été appris, mis à jour, quels thèmes émergent, et ce qui mérite une relecture. Ce skill résume les connaissances, pas les sources — pense à une session de revue hebdomadaire, pas un rapport d'ingestion.

Avant de commencer

  1. Lire ~/.logseq-wiki/config (ou .env local, premier trouvé) → LOGSEQ_VAULT_PATH
  2. Parser la période depuis la requête de l'utilisateur :
    • "quotidien" / "aujourd'hui" / "hier" → dernières 24h
    • "hebdomadaire" / "cette semaine" / sans argument (défaut) → 7 derniers jours
    • "mensuel" / "ce mois" → 30 derniers jours
    • Date ISO "depuis 2026-05-01" → pages mises à jour depuis cette date
    • Nombre explicite "14 derniers jours" → cette durée
  3. Lire $LOGSEQ_VAULT_PATH/wiki/_log.md — 200 dernières lignes — pour les entrées dans la période (timestamps en préfixe ISO-8601)
  4. Si $LOGSEQ_VAULT_PATH/wiki/_insights.md existe, lire son tableau Pages Ancres

Étape 1 : Collecter les pages actives dans la période

Lister tous les .md sous $LOGSEQ_VAULT_PATH/wiki/. Ignorer :

  • wiki/_master-index.md, wiki/_log.md, wiki/_manifest.json
  • Tout ce qui est sous wiki/_meta/, wiki/_archive/
  • Les pages digest elles-mêmes (wiki/journal/digest-*.md)

Pour chaque page restante, lire ses propriétés Logseq (lignes propriété:: valeur en début de fichier) :

  • created:: — date de création
  • updated:: — date de dernière modification

Classer :

  • Nouvelles pages : created:: est dans la période
  • Pages mises à jour : updated:: est dans la période mais created:: est antérieur
  • Inchangées : aucune date dans la période → ignorer

Si moins de 5 pages actives, proposer d'élargir : "Seulement 3 pages actives ces 7 derniers jours — veux-tu un digest mensuel à la place ?"

Pour chaque page active, collecter : title::, tags::, summary::, lifecycle::, les marqueurs ^[ambigu] ou ^[inféré] dans le corps.

Read the full file on GitHub · 190 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. 7d ago First seen · 190 lines · 135 tokens per session scan A 5187a870eda3

Subscribe to this mod's changes

wiki-digest is a skill published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 12d ago), licensed MIT. It adds 135 tokens to every session and 2,233 once invoked, about $0.0007 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