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/wiki-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/wiki-update)<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-update"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-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.00063 | $0.00672 |
| Opus 5 | $0.00032 | $0.00336 |
| Sonnet 5 | $0.00013 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
wiki-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 6d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logseq Update — Mise à jour incrémentale
REQUIRED: Invoke llm-wiki skill first for Logseq syntax and file format rules.
Avant de commencer
- Lire
wiki/_manifest.json— si absent oulast_ingestest null, dire à l'utilisateur de lancerwiki-ingestd'abord pour un ingest complet initial - Lire
wiki/_master-index.mdpour connaître les thèmes existants
Étape 1 : Détecter les changements
Pour chaque source (pages/.md, journals/.md, assets référencés) :
- Calculer le hash actuel :
shasum -a 256 <fichier> | awk '{print $1}' - Comparer au
content_hashdans_manifest.json
Catégoriser :
- Modifiée : hash différent de celui du manifest
- Nouvelle : absente du manifest
- Supprimée : dans le manifest mais fichier introuvable (signaler, ne pas supprimer la page wiki)
- Inchangée : hash identique → skip
Si aucun changement détecté : informer l'utilisateur et s'arrêter.
Annoncer : "X sources modifiées, Y nouvelles, Z supprimées (signalées)"
Pour chaque source modifiée ou nouvelle, appliquer la même logique que wiki-ingest (Étapes 3 à 5), en mode merge :
- Lire la page wiki existante avant d'écrire.
- Intégrer les nouvelles informations sans supprimer l'existant.
- Mettre à jour la propriété
updated::de la page wiki. - Recalculer les ratios
provenance::après intégration des faits. - Recalculer
base_confidence::uniquement si la liste des sources a changé (éviter le churn git). - Ne pas modifier
lifecycle::(préservé pour l'humain). - Si la page est nouvelle, initialiser
lifecycle:: draft,lifecycle_changed:: [DATE],tier:: supporting.
Étape 3 : Signaler les sources supprimées
Pour chaque source supprimée :
- Ne pas supprimer la page wiki correspondante
- Ajouter une note dans la page wiki :
> ⚠️ Source [chemin] introuvable depuis [DATE] - Logger dans
_log.md
Étape 4 : Mettre à jour manifest et log
Mettre à jour _manifest.json pour les sources traitées (hash, timestamp, pages).
Ajouter dans wiki/_log.md :
- [ISO8601] UPDATE — [N] sources modifiées, [M] pages mises à jour, [P] nouvelles pages
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.
- 6d ago First seen · 63 lines · 63 tokens per session scan A a88ab1605706
wiki-update is a skill published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 11d ago), licensed MIT. It adds 63 tokens to every session and 672 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.
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.
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.…
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…
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…
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.