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 odere-pro/claude-wiki-pages-plugin --skill querygit clone --depth 1 https://github.com/odere-pro/claude-wiki-pages-pluginWrote 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/odere-pro/claude-wiki-pages-plugin/query)<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/query"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/query.svg" alt="Measured on agentmods" 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.00070 | $0.02313 |
| Opus 5 | $0.00035 | $0.01156 |
| Sonnet 5 | $0.00014 | $0.00463 |
| Haiku 4.5 | $0.00007 | $0.00231 |
Grade A, and why
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 6d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki — Query
Answer a question from vault/wiki/ with citations back to specific pages.
Unlike a general-purpose search, this skill commits to the wiki's provenance
model: every claim in the answer carries one or more [[wikilink]] citations,
and every cited page must resolve. No hallucinated titles, no paraphrase
without a source.
When to invoke
- The user asks a natural-language question about a topic that might be covered in the wiki.
- An agent (
claude-wiki-pages-analyst-agent) is chaining query as a step.
Do NOT invoke for questions about the plugin itself (how to install, which hooks fire, what a skill does) — those are answered from the docs, not the wiki.
Reading contract
vault/CLAUDE.md— the schema. Read first.vault/wiki/index.md— the top-level catalog. First pass to shortlist candidate pages.vault/wiki/<topic>/<topic>.md— per-folder MOCs (folder notes; legacy_index.mdwhere still present). Second pass to narrow.vault/wiki/<topic>/*.md— candidate typed pages, plus any pages reached by following[[wikilinks]]from them.vault/wiki/_synthesis/*.md— prior syntheses, if relevant.vault/wiki/_sources/*.md— source summaries, when provenance matters to the answer.
C1 — Budget-aware MOC descent (reading engine JSON)
When a search --json candidate set is available (produced by
bash scripts/engine.sh search "<query>" --target <vault> --json), the
descent reads the engine's ranked output and takes a budget-bounded prefix.
Input shape. Each SearchHit in the hits array carries:
| Field | Role in C1 |
|---|---|
score |
Authoritative rank key — the only ordering key C1 uses. |
matched[] |
Read for cut-off explanation and channel-aware tie-breaking. |
wikilink |
Page reference for citation. |
type |
Page type (for display / filter context). |
file |
Vault-relative path used to read the page. |
All five fields are read-only. C1 does not inspect snippet for ranking
purposes.
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.
- 6d ago First seen · 214 lines · 70 tokens per session scan A 259e3dce7d57
query is a skill published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 2,313 once invoked, about $0.0003 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.
Other skills, from other repositories
schema-evolve
This skill should be used when the user asks about 'schema drift', 'schema evolution', 'evolve schema', 'schema sync', 'sync schemas', 'update schema fields', 'schema field frequency', 'missing schema fields', 'unused schema fields', 'schema proposal', 'schema cardinality', 'check schema', 'schema audit', 'schema…
knowledge-maintain
This skill should be used when the user asks to fix, repair, or tidy one or more SPECIFIC named notes — 'fix these notes', 'fix the issues in [note]', 'add the missing relations to [note]', 'tidy up [note]', 'fix orphan [note]', 'apply the gardener findings for [note]'. Applies structural fixes (missing sections…
raindrop-triage
This skill should be used when the user asks to 'triage unsorted bookmarks', 'clean up raindrop inbox', 'sort unsorted', 'organize bookmarks', 'raindrop triage', 'process bookmark backlog', 'promote triaged bookmarks', 'classify triaged', 'raindrop cleanup', 'deduplicate bookmarks', 'find duplicate bookmarks', 'tag…
knowledge-garden
This skill should be used when the user asks to audit, health-check, or structurally validate one or more SPECIFIC named notes or a bounded topic cluster — 'audit these notes', 'check this note for orphans or broken links', 'fourth-wall check on [note]', 'validate the structure of [note]', 'spot-check [note]'. Runs a…
knowledge-prime
This skill should be used when the user asks to 'prime context', 'load project knowledge', 'what do we know about this project', 'knowledge brief', 'project context', 'what packages are documented', 'show coverage for this project', 'dependency coverage report', 'which of our deps have notes', 'knowledge primer'…
nudge
This skill (explicit /nudge only) manages Claude Code feature-adoption nudges sourced from the Basic Memory note main/reference/claude-code-noteworthy-features. Bare /nudge = Mode A (sync): re-read the note, filter out features already marked adopted or declined, and regenerate the tip cache…