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-statusgit 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-status)<a href="https://agentmods.dev/skills/knowz-io/deepseek-knowz-plugin/knowz-status"><img src="https://agentmods.dev/badge/skills/knowz-io/deepseek-knowz-plugin/knowz-status/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/knowz-io/deepseek-knowz-plugin/knowz-status"><img src="https://agentmods.dev/badge/skills/knowz-io/deepseek-knowz-plugin/knowz-status.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.00033 | $0.00448 |
| Opus 5.5 | $0.00013 | $0.00179 |
| Sonnet 5.5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
knowz-status 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 1mo 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-status — Check status
Inspect Knowz MCP health and project routing. Auth for this plugin is KNOWZ_API_KEY (a ukz_ key from https://app.knowz.io/settings/api-keys), not an API key in chat and not /knowz register.
Instructions
- Check whether Knowz tools such as
mcp__knowz__list_vaultsare available. - If available, call
mcp__knowz__list_vaultswithincludeStats: true. - Check project files only (do not hunt pasted keys):
enterprise.jsonknowz-vaults.mdknowz-pending.md
- If tools are missing, tell the user to set
KNOWZ_API_KEY(create aukz_key at https://app.knowz.io/settings/api-keys), install withdsh plugin --profile web add github:knowz-io/deepseek-knowz-pluginif needed, and restartdsh web. Do not paste API keys. Do not run/knowz registeras login. - If tools work but vaults look like the wrong tenant: both rows are using the same key, not a missing second URL. Use two MCP rows with unique
serverNamevalues and two env refs. - Read
knowz-vaults.mdif present and validate listed vault IDs against the server response. - Count pending items in
knowz-pending.mdif it exists. - Report:
- MCP connection status
- server vault count and names
- vault routing file health
- pending capture count
- one concrete next step (set
KNOWZ_API_KEYand restartdsh web, add a second MCP row for another tenant, refreshknowz-vaults.md, or/knowz-flush)
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.
- 1mo ago First seen · 28 lines · 33 tokens per session scan A 483ec6baf57c
knowz-status is a skill published in the GitHub repository knowz-io/deepseek-knowz-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 448 once invoked, about $0.0001 per session on Opus 5.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
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…
dsh-tui-guide
Use when the user asks about dsh-tui itself (usage, shortcuts, config, themes, migration, VS Code). Load before answering; skip for normal coding tasks.
smart-docs
AI-powered comprehensive codebase documentation generator. Analyzes project structure, identifies architecture patterns, creates C4 model diagrams, and generates professional technical documentation. Use when users need to document codebases, understand software architecture, create technical specs, or generate…
deepwiki-rs
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming…
submit-dsh-plugin
A submission checklist and workflow for adding a DeepSeek Harness plugin to the community’s public catalogue. It prepares the catalogue entry and checks the plugin’s repository, metadata, tests, and required files.
dsh-plugin-guide
Use when developing, reviewing, packaging, debugging, or answering questions about DeepSeek Harness (DSH) plugins — the plugin-based agent harness on vendored Cordis. Applies the official plugin-development constraints (plugin contract, cordis.yml layers, services/events/effects, tool DSL, bundles/profiles) backed by…