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.
curl -O https://raw.githubusercontent.com/ystreibel/logseq-wiki/main/.skills/daily-update/SKILL.mdgit clone --depth 1 https://github.com/ystreibel/logseq-wikiWrote 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/ystreibel/logseq-wiki/daily-update)<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/daily-update"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/daily-update.svg" alt="Measured on agentmods" 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.00111 | $0.01506 |
| Opus 5 | $0.00056 | $0.00753 |
| Sonnet 5 | $0.00022 | $0.00301 |
| Haiku 4.5 | $0.00011 | $0.00151 |
Grade A, and why
daily-update 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 8d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Update — Cycle de Maintenance Quotidienne
Tu exécutes une passe de maintenance légère sur le wiki : vérifier la fraîcheur des sources, rafraîchir l'index, régénérer le contexte chaud, et écrire le fichier d'état que la notification terminal lit.
Avant de commencer
- Lire
~/.logseq-wiki/config(ou.envlocal) →LOGSEQ_VAULT_PATH,LOGSEQ_WIKI_REPO - Dériver le répertoire d'état scopé au vault :
VAULT_ID=$(echo "$LOGSEQ_VAULT_PATH" | md5sum 2>/dev/null | cut -c1-8 \ || md5 -q - <<< "$LOGSEQ_VAULT_PATH" | cut -c1-8) STATE_DIR="$HOME/.logseq-wiki/state/$VAULT_ID" mkdir -p "$STATE_DIR" - Lire
$LOGSEQ_VAULT_PATH/wiki/_manifest.json
Modes
Mode Run (défaut — déclenché par cron ou /daily-update)
Exécuter le cycle de maintenance :
Étape 1 : Vérification de fraîcheur des sources
Comparer chaque source dans _manifest.json avec le temps de modification du fichier.
Classifier comme :
- Fraîche —
mtime ≤ ingested_at - Périmée —
mtime > ingested_at(nouveau contenu existe, pas encore ingéré) - Manquante — le fichier source n'existe plus
Étape 2 : Rafraîchissement de l'index
Lire $LOGSEQ_VAULT_PATH/wiki/_master-index.md. Si des pages du vault manquent dans
l'index (ou inversement), mettre à jour l'index. Utiliser :
find "$LOGSEQ_VAULT_PATH/wiki" -name "*.md" \
! -path "*/wiki/_*" ! -name "_master-index.md"
pour énumérer les pages wiki, puis réconcilier avec l'index.
Étape 3 : Mise à jour du contexte chaud
Lire les 200 dernières lignes de wiki/_log.md (contexte de session). Si le dernier
log date de plus de 48h, lire les 10 pages wiki les plus récemment modifiées et écrire
un snapshot sémantique de ~300 mots en bas de wiki/_log.md sous la section :
## Contexte chaud — <YYYY-MM-DD>
<snapshot>
Étape 4 : Écriture de l'état
Écrire dans $STATE_DIR :
date +%s > "$STATE_DIR/.last_update"
echo "<nombre_sources_périmées>" > "$STATE_DIR/.pending_delta"
echo "$LOGSEQ_VAULT_PATH" > "$STATE_DIR/.vault_path"
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.
- 8d ago First seen · 159 lines · 111 tokens per session scan A 820eee61a2bd
daily-update is a skill published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 12d ago), licensed MIT. It adds 111 tokens to every session and 1,506 once invoked, about $0.0006 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.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
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…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.