What is llmwiki-query?

A skill that answers questions by searching the user's local llmwiki, a knowledge base built from their past coding sessions.

Use it to ask what was decided, how a problem was solved, or what work was done in earlier sessions.

It makes past decisions, fixes, preferences, and project work easier to find without rereading old transcripts.

How Pratiyush/llm-wiki configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Pratiyush/llm-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/Pratiyush/llm-wiki/master/.claude/skills/llmwiki-query/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Pratiyush/llm-wiki

Made for: Claude Code.

Or install llm-wiki, the plugin that ships this one along with the rest of its 6 skills, 18 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pratiyush/llm-wiki/llmwiki-query/github.svg)](https://agentmods.dev/skills/pratiyush/llm-wiki/llmwiki-query)

Your own site

<a href="https://agentmods.dev/skills/pratiyush/llm-wiki/llmwiki-query"><img src="https://agentmods.dev/badge/skills/pratiyush/llm-wiki/llmwiki-query/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pratiyush/llm-wiki/llmwiki-query"><img src="https://agentmods.dev/badge/skills/pratiyush/llm-wiki/llmwiki-query.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 656 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00087	$0.00656
Opus 5	$0.00044	$0.00328
Sonnet 5	$0.00017	$0.00131
Haiku 4.5	$0.00009	$0.00066

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

Security

Grade A, and why

llmwiki-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 10d 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.

.claude/skills/llmwiki-query/SKILL.md · 65 lines

How it starts

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

llmwiki-query

What this skill does

Reads the user's local llmwiki (llmwiki/wiki/) and synthesises an answer to their question, with [[wikilink]] citations pointing to the source pages.

When to use

Invoke this skill when the user asks a question about their own work or history. Examples:

"What did I decide about the AiShorts backend?"
"What MCP servers do I have configured?"
"How did I fix the X bug last week?"
"What's my preferred way to ingest sessions?"
"What have I been working on in the germanly project?"

Do NOT invoke for questions that can be answered without the user's personal knowledge base (e.g., "how does TCP work?" → answer from general knowledge).

Workflow

Follow the Query Workflow from the repo's CLAUDE.md:

Locate the llmwiki install (see llmwiki-sync skill for the fallback search order).
Read wiki/index.md to identify the set of pages that might be relevant.
Read wiki/overview.md to get the living synthesis context.
Pick the most relevant pages (sources, entities, concepts) based on the question.
Read those pages with the Read tool.
Synthesise an answer with inline [[wikilink]] citations. Quote directly from source pages when the wording matters.
If the answer is substantial (3+ paragraphs), ask the user whether to save it as a synthesis page:
```
Would you like me to save this as wiki/syntheses/<slug>.md for future reference?
```
If yes, write it using the Synthesis Page Format from CLAUDE.md.

Append to wiki/log.md:

## [YYYY-MM-DD] query | <short question>

Fallback behavior

If the wiki has no relevant pages:

Tell the user "I don't see anything about this in your wiki yet."
Suggest running /wiki-sync to pull in any recent sessions that might cover the topic.
If the topic is unlikely to be in session history, offer to answer from general knowledge (and make that explicit: "this is general knowledge, not from your wiki").

Read the full file on GitHub · 65 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.

10d ago First seen · 65 lines · 87 tokens per session scan A 31dd7b1dd77d

Subscribe to this mod's changes

llmwiki-query is a skill published in the GitHub repository Pratiyush/llm-wiki (387 stars, last pushed 2mo ago), licensed MIT. It adds 87 tokens to every session and 656 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-30.

Claude Code Memory and context ai codex-cli cursor developer-tools karpathy

handover

Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".

jazzyalex/agent-sessions · 71 tokens

init-workspace-documentation

Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.

griddynamics/rosetta · 10 tokens

ijfw-memory-audit

Audit and clean project memory files. Trigger: 'memory audit', 'clean memory', 'memory health', /memory-audit.

FerroxLabs/ijfw · 31 tokens

ijfw-handoff

Session handoff generation and loading. Trigger: session end, context full, /handoff.

FerroxLabs/ijfw · 23 tokens

ijfw-summarize

Generate optimized project context from codebase scan. Trigger: new project, no CLAUDE.md, /ijfw-summarize.

FerroxLabs/ijfw · 32 tokens

repo-context-ledger

Record every behavior-changing feature addition, fix, and adjustment as durable, evidence-based repository knowledge, then use that ledger to continue accurately across AI windows, tools, Git collaboration, and pull requests. Use the deterministic runtime to route bounded context, isolate private drafts, publish…

gviiisen/repo-context-ledger · 98 tokens

llm-wiki: Skill for Claude Code