agentmods.dev

logseq-wiki: Skill for Claude Code

.skills/wiki-research/SKILL.md

wiki-research is a skill for Claude Code, Codex from ystreibel/logseq-wiki. It costs 83 tokens per session (1,517 once invoked), scanned A, original, MIT.

A multi-step web research workflow that investigates a topic, summarizes the findings, and saves organized pages in a Logseq wiki. Logseq is a linked note-taking system used as a persistent knowledge base.

In plain words
What is it for?
Use it for broad topic research, source collection, cross-source synthesis, and depositing the results as permanent wiki pages.
Why use it?
It turns scattered online research into structured notes that can be searched and reused later. It also checks existing wiki coverage before researching again.

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 →

not rated 4repo 12d ago A scan 83 tokens original MIT
View source ↗ ystreibel/logseq-wiki
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-research/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-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-research.svg)](https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-research)
Your own site
<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-research"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-research.svg" alt="Measured on agentmods" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,517 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.00083 $0.01517
Opus 5 $0.00042 $0.00758
Sonnet 5 $0.00017 $0.00303
Haiku 4.5 $0.00008 $0.00152

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

Security

Grade A, and why

wiki-research 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.

.skills/wiki-research/SKILL.md · 172 lines

How it starts

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

Wiki Research — Recherche Autonome Multi-Round

Tu exécutes une boucle de recherche autonome sur un sujet, synthétises ce que tu trouves, et déposes les résultats dans le wiki Logseq comme connaissance permanente.

Avant de commencer

  1. Lire ~/.logseq-wiki/config (ou .env local, premier trouvé) → LOGSEQ_VAULT_PATH
  2. Lire $LOGSEQ_VAULT_PATH/wiki/_master-index.md pour comprendre ce qui est déjà dans le wiki — ne pas re-rechercher des sujets bien couverts
  3. Lire $LOGSEQ_VAULT_PATH/wiki/_log.md (hot context) si disponible

Confirmer le sujet de recherche avec l'utilisateur s'il est ambigu. Puis procéder.

Configuration de recherche (optionnelle)

Si $LOGSEQ_VAULT_PATH/wiki/_meta/research-config.md existe, le lire et appliquer :

  • Préférences de sources (ex: préférer académique, éviter certains domaines)
  • Domaines à ignorer
  • Ajustements de scoring de confiance
  • Contraintes spécifiques au sujet

Round 1 — Survey Large

Objectif : Cartographier le sujet.

  1. Décomposer le sujet en 3-5 angles distincts
  2. Pour chaque angle, lancer 2-3 requêtes WebSearch avec des formulations variées
  3. Pour les 2-3 meilleurs résultats par angle, fetcher le contenu
  4. De chaque page fetchée, extraire :
    • Claims clés — ce que la source dit explicitement
    • Concepts — idées, termes, frameworks introduits
    • Entités — outils, personnes, organisations mentionnés
    • Contradictions — là où les sources se contredisent

Suivre ce qui est couvert et ce qui manque au fur et à mesure.

Round 2 — Combler les lacunes

Objectif : Fermer les trous du Round 1.

Relire ce que le Round 1 a produit :

  • Quelles questions les sources ont-elles soulevées sans répondre ?
  • Où les sources se contredisent-elles ?
  • Quels angles ont été peu couverts ?

Lancer jusqu'à 5 recherches ciblées sur ces lacunes. Préférer les sources primaires, la documentation officielle, les analyses de référence.

Mettre à jour le working set. Mettre à jour la liste de contradictions.

Read the full file on GitHub · 172 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. 8d ago First seen · 172 lines · 83 tokens per session scan A 8b78f58843cb

Subscribe to this mod's changes

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

ResearchWriting and docs
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-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 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