Borrowing it
Nothing to install: this file belongs to bradduy/wiki-knowledge-compiler. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bradduy/wiki-knowledge-compiler/main/.claude/commands/wiki-insights.mdgit clone --depth 1 https://github.com/bradduy/wiki-knowledge-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/bradduy/wiki-knowledge-compiler/wiki-insights)<a href="https://agentmods.dev/commands/bradduy/wiki-knowledge-compiler/wiki-insights"><img src="https://agentmods.dev/badge/commands/bradduy/wiki-knowledge-compiler/wiki-insights.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.00011 | $0.00985 |
| Opus 5 | $0.00005 | $0.00492 |
| Sonnet 5 | $0.00002 | $0.00197 |
| Haiku 4.5 | $0.00001 | $0.00098 |
Grade A, and why
wiki-insights 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Insights
You are the wiki-synthesizer. Your job is to read across the knowledge base and identify non-obvious connections, patterns, and gaps.
Input
Optional focus: $ARGUMENTS
If no focus is provided, perform a broad scan.
Procedure
Step 1: Read broadly
- Read
.data/index/master-index.mdfor an overview. - Read all topic pages in
.data/topics/. - Read all existing insight pages in
.data/insights/. - Read entity pages in
.data/entities/— walk their relationships to find structural connections. - If a focus area is provided, also read relevant concept and summary pages.
Step 2: Identify cross-cutting patterns
Look for:
- Recurring themes across different sources that aren't yet captured in a single place
- Contradictions between sources (explicit disagreements or incompatible assumptions)
- Knowledge gaps — areas where multiple sources touch on a topic but none covers it fully
- Unexpected connections between concepts from different domains or sources
- Emerging patterns — trends visible only when viewing multiple sources together
Step 3: Draft insights
For each insight identified:
- Write it using
templates/insight.md. - Every claim must cite specific wiki pages.
- Rate the insight:
confidence: high— directly supported by multiple sourcesconfidence: medium— reasonable inference from available evidenceconfidence: low— speculative, based on partial evidence
- Mark any speculative leaps with
[speculative: reason].
Step 4: Check for redundancy
Before writing an insight:
- Search existing
insights/for similar content. - If a similar insight exists, update it rather than creating a duplicate.
- If the new insight contradicts an existing one, note the contradiction in both.
Step 5: Identify knowledge gaps
Create a section listing:
- Topics mentioned across multiple sources but with no dedicated concept or topic page
- Questions raised by the synthesis that the wiki cannot currently answer
- Areas where adding one more source would significantly improve coverage
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 · 128 lines · 11 tokens per session scan A da6737895f36
wiki-insights is a command published in the GitHub repository bradduy/wiki-knowledge-compiler (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 985 once invoked, about $0.0001 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-30.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.