agentmods.dev

wiki-query

wiki-query is a skill for Claude Code, Codex from PLATZDORSCH/wiki-hermes. It costs 20 tokens per session (592 once invoked), scanned A, original, MIT.

A skill for answering questions from a compiled internal wiki. It finds relevant pages, combines their information, and points to sources or uncertainties.

In plain words
What is it for?
Use it to research a topic in the wiki, assess or compare information, and save substantial analyses as linked synthesis pages.
Why use it?
It helps avoid answering from scattered notes or memory. It also makes gaps, conflicting information, and limited evidence visible.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 10repo 5mo ago A scan 20 tokens original MIT

Good fit Use it to research a topic in the wiki, assess or compare information, and save substantial analyses as linked synthesis pages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/platzdorsch/wiki-hermes/wiki-query
View source ↗ PLATZDORSCH/wiki-hermes platzdorsch.de
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add PLATZDORSCH/wiki-hermes --skill wiki-query
Clone the repo
git clone --depth 1 https://github.com/PLATZDORSCH/wiki-hermes

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/platzdorsch/wiki-hermes/wiki-query/github.svg)](https://agentmods.dev/skills/platzdorsch/wiki-hermes/wiki-query)
Your own site
<a href="https://agentmods.dev/skills/platzdorsch/wiki-hermes/wiki-query"><img src="https://agentmods.dev/badge/skills/platzdorsch/wiki-hermes/wiki-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.

agentmods 80×15 button for wiki-query

Your own site · 80×15
<a href="https://agentmods.dev/skills/platzdorsch/wiki-hermes/wiki-query"><img src="https://agentmods.dev/badge/skills/platzdorsch/wiki-hermes/wiki-query.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 592 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.00020 $0.00592
Opus 5 $0.00010 $0.00296
Sonnet 5 $0.00004 $0.00118
Haiku 4.5 $0.00002 $0.00059

Measured 9d ago against content hash 26e07493a909, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 9d 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 · 68 lines

How it starts

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

wiki-query

Beantworte eine Frage auf Basis des kompilierten Wiki-Wissens.

When to Use

  • User stellt eine inhaltliche Frage zur Branche
  • User will eine Einschätzung, Analyse oder Einordnung
  • User sagt "was wissen wir über...", "wie steht es um..." o.ä.

Procedure

  1. Index lesen — wiki/index.md lesen, um relevante Seiten zu identifizieren.

  2. Relevante Seiten lesen — Alle thematisch passenden Wiki-Seiten lesen. Bei Unsicherheit lieber zu viele als zu wenige.

  3. Antwort synthetisieren — Antwort formulieren mit:

    • Verweisen auf Wiki-Seiten als Belege
    • Kennzeichnung wenn etwas auf wenigen Quellen basiert
    • Markierung von Widersprüchen oder Unsicherheiten

  4. Speichern prüfen — Falls die Antwort substanziell ist (Analyse, Vergleich, neue Erkenntnis): als neue Seite in wiki/synthesis/ speichern:

    ---
title: "Analyse: Thema"
category: synthesis
created: YYYY-MM-DD
updated: YYYY-MM-DD
tags: [relevante, tags]
sources: [referenzierte-seiten.md]
status: active
---

    Die Seite braucht einen "Verwandte Seiten"-Abschnitt mit mindestens 2 bidirektionalen Links.

  5. ⛔ Index, Overview und Log aktualisieren — Falls eine neue Seite erstellt wurde:

    • wiki/index.md → neuen Eintrag unter Synthesis
    • wiki/overview.md → falls die Analyse neue Erkenntnisse enthält
    • wiki/log.md → Eintrag mit query | Fragetitel

Pitfalls

  • Immer zuerst den Index lesen, nie direkt raten
  • Wenn das Wiki keine ausreichende Antwort hergibt: offen sagen und Quellenlücken benennen
  • Triviale Fragen müssen nicht als Synthesis-Seite gespeichert werden
  • Falls gespeichert: Index, Overview und Log NIEMALS vergessen

Verification

⛔ BEVOR du den Workflow als abgeschlossen meldest:

  1. Antwort basiert auf tatsächlichen Wiki-Seiten, nicht auf Allgemeinwissen
  2. Falls gespeichert: neue Seite hat korrektes Frontmatter UND "Verwandte Seiten"-Abschnitt
  3. Falls gespeichert: wiki/index.md enthält die neue Seite
  4. Falls gespeichert: wiki/log.md hat einen Eintrag
  5. Erst dann dem User Abschluss melden.

Read the full file on GitHub · 68 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. 9d ago First seen · 68 lines · 20 tokens per session scan A 26e07493a909

Subscribe to this mod's changes

wiki-query is a skill published in the GitHub repository PLATZDORSCH/wiki-hermes (10 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 592 once invoked, about $0.0001 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.

Research
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