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 agentmods add skills/rossoctl/examples/wiki-query-mcpnpx skills add rossoctl/examples --skill wiki-query-mcpgit clone --depth 1 https://github.com/rossoctl/examplesWhat 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 | $0.00000 | $0.00632 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
wiki-query-mcp 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kwiki Query Agent (MCP)
Query the wiki memory service to find and read information on behalf of a user.
Prerequisites
The wiki-memory MCP server must be registered and running (stdio or streamable-http on port 8322).
Procedure
-
List available topics — Call
wiki_list_topicsto see what topics exist and their page counts. -
Search for information — Call
wiki_querywith:topic_id: the topic to search (e.g. "ai", "security")query: natural language search termslimit: max results (default 10)
-
Search across all topics — Call
wiki_search_allwith:query: search termslimit: max results (default 10)
-
Read specific pages — Call
wiki_readwith:topic_id: the topicpath: page filename (e.g. "transformers.md") Returns content with frontmatter metadata.
-
Activity feed — Call
wiki_activitywith:topic_id: (optional) specific topic, or empty for globallimit: max entries (default 20)
-
Find backlinks — Call
wiki_backlinkswith:topic_id: the topicpath: page to find references to
-
Browse by tags — Call
wiki_list_tagswithtopic_id, orwiki_pages_by_tagwithtopic_idandtag. -
Page graph — Call
wiki_graphwithtopic_idto get nodes and edges. -
List drafts — Call
wiki_list_draftswithtopic_id. -
Get templates — Call
wiki_get_templatewith optionaltemplate_id.
Example Flow
wiki_list_topics → "ai (4 pages), security (0 pages)"
wiki_query(topic_id="ai", query="attention mechanism") → ranked results
wiki_search_all(query="transformer") → results across all topics
wiki_read(topic_id="ai", path="transformers.md") → content + frontmatter
wiki_activity(topic_id="ai") → recent commits
wiki_backlinks(topic_id="ai", path="transformers.md") → pages linking here
wiki_list_tags(topic_id="ai") → tags with counts
wiki_pages_by_tag(topic_id="ai", tag="paper") → pages with tag
wiki_graph(topic_id="ai") → {"nodes": [...], "edges": [...]}
wiki_list_drafts(topic_id="ai") → pending drafts
wiki_get_template(template_id="paper-summary") → template content
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.
- 2d ago First seen · 64 lines · 0 tokens per session scan A 6f2f4a379d5b
wiki-query-mcp is a skill published in the GitHub repository rossoctl/examples (11 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 632 tokens. 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.
Other skills, from other repositories
importing-a-codebase
Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
spec-graph
The project's specs are its ground truth: durable documents describing the architecture, decisions, contracts, and boundaries behind the code, organized as a connected graph. Read this skill and reach for the spec tools FIRST — before reading code — whenever you explore the project, plan or start a task, add or change…
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.