logseq-wiki: Skill for Claude Code

.skills/wiki-query/SKILL.md

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

A search and answer tool for a compiled Logseq wiki. It finds relevant pages in a personal knowledge base and can combine them into answers with citations to the wiki.

In plain words
What is it for?
Use it to answer questions about the wiki, find everything related to a topic, and produce synthesized answers based on stored pages.
Why use it?
It avoids manually opening many linked notes to find related information. It can also restrict results to user-facing content when requested.

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-query/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-query

README.md
[![agentmods](https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-query.svg)](https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-query)
Your own site
<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-query"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-query.svg" alt="Measured on agentmods" height="20"></a>
Per session 144 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,392 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.00144 $0.02392
Opus 5 $0.00072 $0.01196
Sonnet 5 $0.00029 $0.00478
Haiku 4.5 $0.00014 $0.00239

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

Security

Grade A, and why

wiki-query 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-query/SKILL.md · 153 lines

How it starts

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

Wiki Query — Interrogation du vault Logseq

REQUIRED: Invoke llm-wiki skill first for Logseq syntax and file format rules.

You are answering questions against a compiled Logseq wiki, not raw source documents. The wiki contains pre-synthesized, cross-referenced knowledge.

Before You Start

  1. Resolve config — read ~/.logseq-wiki/config first (works cross-project); fall back to .env in the logseq-wiki repo. This gives LOGSEQ_VAULT_PATH.
  2. If $LOGSEQ_VAULT_PATH/wiki/_hot.md exists, read it first — it gives instant context on recent activity. If the user's question is about something ingested recently, _hot.md may answer it before you even open _master-index.md.
  3. Read $LOGSEQ_VAULT_PATH/wiki/_master-index.md to understand the wiki's scope and structure.

Visibility Filter (optional)

By default, all pages are returned regardless of visibility tags. This preserves existing behavior — nothing changes unless the user asks for it.

If the user's query includes phrases like "public only", "user-facing", "no internal content", "as a user would see it", or "exclude internal", activate filtered mode:

  • Build a blocked tag set: {visibility/internal, visibility/pii}
  • In the Index Pass (Step 2), skip any candidate whose tags:: property contains a blocked tag
  • In Section/Full Read passes (Steps 3–4), do not read or cite any blocked page
  • Synthesize the answer only from allowed pages — do not mention that excluded pages exist

Pages with no visibility/ tag, or tagged visibility/public, are always included.

In filtered mode, note the filter in the Step 6 log entry: mode=filtered.

Retrieval Protocol

Follow the Retrieval Primitives table in llm-wiki/SKILL.md. Reading is the dominant cost of this skill — use the cheapest primitive that answers the question and escalate only when it can't. Never jump straight to full-page reads.

Step 1: Understand the Question

Classify the query type:

  • Factual lookup — "What is X?" / "Qu'est-ce que X ?" → Find the relevant page(s)
  • Relationship query — "How does X relate to Y?" / "What contradicts X?" → Find both pages, their cross-references, and their relationships:: property for typed edges
  • Synthesis query — "What's the current thinking on X?" / "Résume tout ce que je sais sur X" → Find all pages that touch X, synthesize
  • Gap query — "What don't I know about X?" → Find what's missing, check open questions sections
  • Decision ("qu'a-t-on décidé sur X ?") → search wiki pages + journals
  • Temporal ("que s'est-il passé en avril ?") → search journals by period

Read the full file on GitHub · 153 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 · 153 lines · 144 tokens per session scan A 191eb2cbf32d

Subscribe to this mod's changes

wiki-query is a skill published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 12d ago), licensed MIT. It adds 144 tokens to every session and 2,392 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens