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.
npx skills add ihudak/ihudak-claude-plugins --skill wiki-querygit clone --depth 1 https://github.com/ihudak/ihudak-claude-pluginsWrote 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/ihudak/ihudak-claude-plugins/wiki-query)<a href="https://agentmods.dev/skills/ihudak/ihudak-claude-plugins/wiki-query"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/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.
<a href="https://agentmods.dev/skills/ihudak/ihudak-claude-plugins/wiki-query"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/wiki-query.svg" alt="Reviewed on agentmods" width="80" 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.00087 | $0.00911 |
| Opus 5 | $0.00044 | $0.00456 |
| Sonnet 5 | $0.00017 | $0.00182 |
| Haiku 4.5 | $0.00009 | $0.00091 |
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 4d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-query
Read skills/wiki-schema/SKILL.md fully before proceeding.
Invoke with: /wiki-query <question>
Step 1 — Resolve VAULT_PATH
Vault path: ~/obsidian_vault by default; set VAULT_PATH to override. WSL users with a Windows-side vault must set VAULT_PATH explicitly (e.g. /mnt/c/Users/<name>/obsidian_vault).
Step 2 — Load recent context
Read wiki/hot.md if it exists. If the file is absent or empty, skip silently.
If it contains a directly relevant answer or strong context clues, use that to guide which
pages to read.
Step 3 — Choose search path
Path A — qmd MCP (Claude Code, when qmd collection is registered)
Check if qmd has a wiki collection:
mcp__plugin_qmd_qmd__status
If the wiki collection is listed in the status output, use Path A. Otherwise use Path B.
Path A steps:
-
Run a hybrid search against the wiki collection:
mcp__plugin_qmd_qmd__query searches: [{type: "lex", query: "<keywords>"}, {type: "vec", query: "<question>"}] intent: "<question>" minScore: 0.4 -
Also check if a
meetingsorsourcescollection is registered. If the question is about specific events, decisions, or people, run an additional query against those collections and merge the results. -
Retrieve the top-scoring pages:
mcp__plugin_qmd_qmd__get path: "<result filepath>" -
Read the returned pages fully. Proceed to Step 4.
Path B — Index-guided reading (Copilot, or qmd not configured)
- Read
wiki/_index.mdfully. - Scan the index summary column for entries relevant to the question.
- Read up to 5 most relevant pages. Prioritise by: direct title match, then tag match, then summary match.
- If 5 pages are not enough to answer confidently, read up to 3 more. Do not read the entire wiki.
Step 4 — Synthesise the answer
Write the answer in declarative present tense. Cite every claim:
- For wiki pages:
(→ [[concepts/MCP Server]]) - For original source files:
(→ [[Meetings/MGD/2026-04-10 MCP Planning.md]]) - For multiple sources: list all
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.
- 4d ago First seen · 122 lines · 87 tokens per session scan A 3df40f288bb8
wiki-query is a skill published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 911 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-09-05.
Other skills, from other repositories
competitive-battlecard
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
sheet-music-publisher
Converts mastered audio to sheet music and creates printable songbooks. Use after mastering when the user wants sheet music or a songbook for their album.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.
prohibit-bad-habits
Use when a user wants to define patterns the agent should not do. Don't use for remote, credential, publish, deploy, or irreversible changes.
linear
Read Linear Issues and Projects via the GraphQL API. Supports fetching individual issues (title, description, identifier, sub-issues, owning project), fetching all issues in a project, verifying credentials, and executing confirmed refresh write-back actions through work-intake. Use when you want to read Linear work…