Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ussumant/llm-wiki-compiler/plugin install llm-wiki-compilerWrote 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/commands/ussumant/llm-wiki-compiler/wiki-visualize)<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-visualize"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-visualize.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.00000 | $0.00258 |
| Opus 5 | $0.00000 | $0.00129 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
wiki-visualize 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.
What it actually says
Visualize Wiki Knowledge Graph
Launch an interactive canvas-based knowledge graph of your compiled wiki. Topics appear as nodes, concepts as connecting edges. Click any node to read the article.
Instructions
-
Check that
.wiki-compiler.jsonexists in the project root -
Check that the wiki has been compiled (output directory has
INDEX.md) -
If not compiled, suggest running
/wiki-compilefirst -
Start the visualization server:
node "${CLAUDE_PLUGIN_ROOT}/visualize/server.js" --wiki-dir "{output_path}" -
Open the browser:
open "http://localhost:3848" -
Tell the user:
📊 Wiki Knowledge Graph running at http://localhost:3848 - Click nodes to read topic articles - Hover edges to see concept connections - Search to filter topics - The server reads your wiki files live — changes from /wiki-compile appear immediately Stop with Ctrl+C when done.
Arguments
- (none) — launch visualization for current project's wiki
--port {number}— use a custom port (default: 3848)
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 · 37 lines · 0 tokens per session scan A ac8af4605583
wiki-visualize is a command published in the GitHub repository ussumant/llm-wiki-compiler (321 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 258 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 commands, from other repositories
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
can-i-use
Check browser support for web platform features against the project's browser targets.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
verify-pr
Verify a PR's frontend changes through browser automation.