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 knowz-io/deepseek-knowz-plugin --skill knowz-askgit clone --depth 1 https://github.com/knowz-io/deepseek-knowz-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/knowz-io/deepseek-knowz-plugin/knowz-ask)<a href="https://agentmods.dev/skills/knowz-io/deepseek-knowz-plugin/knowz-ask"><img src="https://agentmods.dev/badge/skills/knowz-io/deepseek-knowz-plugin/knowz-ask.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.00043 | $0.00457 |
| Opus 5 | $0.00022 | $0.00229 |
| Sonnet 5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
knowz-ask 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 7d 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.
What it actually says
/knowz-ask — Vault Q&A
Answer the user's question using Knowz vaults.
If enterprise.json exists in the project root, use its brand value instead of "Knowz" in user-facing text.
Instructions
- Read
knowz-vaults.mdfrom the project root if it exists.- If it does not exist, continue without vault routing and suggest
/knowz-setupafter the answer.
- If it does not exist, continue without vault routing and suggest
- Parse the user's question.
- Route to the best vaults using each vault's
When to queryrules.- One match → query that vault.
- Multiple matches → query all matching vaults.
- No match → use the default vault when available.
- Query directly from the current agent. Do not assume helper reader agents.
- One target vault → call
mcp__knowz__ask_questiononce withvaultId - Multiple target vaults → issue one
mcp__knowz__ask_questioncall per vault, in parallel when the runtime supports it, then synthesize agreements and conflicts - No specific vault → call
mcp__knowz__ask_questiononce withoutvaultIdor against the default vault when known - Set
researchMode: truefor multi-part, comparative, architectural, or "why" questions; otherwisefalse
- One target vault → call
- If the answer is still too thin, open the top cited items with
mcp__knowz__get_knowledge_itembefore responding. - Answer naturally and mention which vaults informed the result when possible. Frame vault knowledge as point-in-time and to be verified, not current fact — prefer the live source when it conflicts with a vault entry.
If Knowz MCP tools are unavailable, report: "{brand} MCP not connected. In Grok Bot Plugins or Cursor Marketplace, search Knowz → Add → Authorize. Do not paste API keys in chat."
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.
- 7d ago First seen · 30 lines · 43 tokens per session scan A 2ba9ef6d23fc
knowz-ask is a skill published in the GitHub repository knowz-io/deepseek-knowz-plugin (1 stars, last pushed 21d ago), licensed MIT. It adds 43 tokens to every session and 457 once invoked, about $0.0002 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
krouter-obsidian
KRouter Obsidian — route knowledge-dependent tasks to the smallest current evidence set in an Obsidian vault using deterministic local search. Use when a request depends on durable user preferences, prior corrections or superseded claims, long-term project history or results, reusable methods or evidence, or the…
knowledge-wiki
Manage the personal knowledge wiki. Use when the user shares articles, documents, or asks to organize knowledge; when a conversation produces insights worth preserving as structured knowledge; or when the user asks about the knowledge base.
modlens
Plug-in vision for text-only models. Hard rule: when a file path or URL with an image extension (.png, .jpg, .jpeg, .webp, .gif, .heic, .heif) appears anywhere in the conversation (typed by the user, injected as a [Image: source: ] line, or inside a tag) and you cannot see that image's content, run this skill on it…
j-space
Use this skill to establish and operate the model's inner workspace — the J-space — for any task that needs more than fluent output: multi-step or chained reasoning, planning, long-horizon and agentic work, competition-level problems, complex debugging, keeping many parts of a deliverable globally consistent, holding…
install-openviking-memory
Install and configure the OpenViking long-term memory plugin for OpenClaw via natural conversation. Once installed, the plugin automatically captures facts from chats and recalls relevant context before each reply (auto-capture + auto-recall, cross-session). Covers prerequisites, install through OpenClaw's plugin…
openviking-context-database
Use OpenViking from OpenClaw through @openviking/openclaw-plugin: long-term memory, session archives, resource and Agent Skill import, semantic recall, recall trace debugging, and externalized tool-result recovery. Prefer this skill when the user wants to use, query, debug, or operate OpenViking context from an…