llm-wiki-newsroom: Command for Claude Code

.claude/commands/wiki-discover.md

wiki-discover is a command for Claude Code from alfadur7/llm-wiki-newsroom. It costs 0 tokens per session (1,571 once invoked), scanned A, original, MIT.

A command for finding unexpected links and missing connections in an LLM Wiki, a linked collection of pages about people, ideas, and sources.

In plain words
What is it for?
Use it to explore from a chosen topic, select a random or surprising starting point, or diagnose gaps such as single-source pages, orphaned claims, and stale hubs.
Why use it?
It helps you discover related topics that a direct search may miss and identify weak, isolated, outdated, or underdeveloped areas in the wiki.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is alfadur7/llm-wiki-newsroom's own configuration. It tells Claude Code how to work on llm-wiki-newsroom itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything llm-wiki-newsroom configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alfadur7/llm-wiki-newsroom. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/alfadur7/llm-wiki-newsroom/main/.claude/commands/wiki-discover.md
Clone the repo
git clone --depth 1 https://github.com/alfadur7/llm-wiki-newsroom

Made for: Claude Code.

Wrote 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.

agentmods badge for wiki-discover

README.md
[![agentmods](https://agentmods.dev/badge/commands/alfadur7/llm-wiki-newsroom/wiki-discover/github.svg)](https://agentmods.dev/commands/alfadur7/llm-wiki-newsroom/wiki-discover)
Your own site
<a href="https://agentmods.dev/commands/alfadur7/llm-wiki-newsroom/wiki-discover"><img src="https://agentmods.dev/badge/commands/alfadur7/llm-wiki-newsroom/wiki-discover/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.

agentmods 80×15 button for wiki-discover

Your own site · 80×15
<a href="https://agentmods.dev/commands/alfadur7/llm-wiki-newsroom/wiki-discover"><img src="https://agentmods.dev/badge/commands/alfadur7/llm-wiki-newsroom/wiki-discover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,571 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01571
Opus 5.5 $0.00000 $0.00628
Sonnet 5.5 $0.00000 $0.00314
Haiku 4.5 $0.00000 $0.00157

Measured 13d ago against content hash 840b19e47e69, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wiki-discover 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 13d 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.

.claude/commands/wiki-discover.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Discover unexpected connections in the LLM Wiki (Memex serendipity).

Usage: /wiki-discover <seed | --random | --surprising | --gaps [<slug>]>

If $ARGUMENTS is empty: print the usage below and stop.

Usage: /wiki-discover <seed | --random | --surprising | --gaps [<slug>]>

Examples:
  /wiki-discover Meta             # start from a specific entity
  /wiki-discover AgenticAI        # start from a concept page
  /wiki-discover --random         # random seed among mid-band backlink hubs
  /wiki-discover --surprising     # auto-rank top N bridge hubs by composite score
  /wiki-discover --gaps           # 9-type gap diagnosis + Track A/B/C/D split commentary
  /wiki-discover --gaps synthesis # only a specific gap type

gap slug: single-source · stale-hub (A) · bridge (B) · orphan-claims · cap-theme · stale-theme (C) · synthesis · trail · timeline (D).

Traversal Pattern

Reading domain — Meta (graph-traversal tools) + supporting Reporter commentary.

Cycle Owner Action
Trigger Editor-in-Chief slash → mode branch (Mode 1: Seed Discovery / Mode 2: Surprising Bridge Hubs / Mode 3: Gap Inventory)
Graph traversal Meta (tools/discover.py · tools/lint.py graph gaps · wiki/_backlinks.json) seed identification · 2-hop exploration · bridge ranking · gap diagnosis
Surface Reporter (mode=ground) discovered connections + gap commentary
(optional) Follow-up Editor-in-Chief when the human reviewer has intent, route via re-running the seed · a deeper /wiki-query · /wiki-news --gap · a /wiki-ingest chain (procedure in the ## Follow-up section below)

Mode 1: Seed Discovery (<seed> or --random)

  1. Load wiki/_backlinks.json
  2. Select the seed:
    • If a seed argument is given, use that entity/concept
    • If --random, pick a random mid-band hub with backlinks in the 5–30 range
  3. 2-hop exploration — read the seed page → read the top 5 pages by seed backlinks → identify pages among the common references that are not directly connected to the seed
  4. Output format:
    ## 🔍 Discovery: starting from [seed page]
    
    ### Unexpected connections
    1. **[[PageA]]** ← [1-2 sentences on why it connects]
    ...
    
    ### Suggested explorations
    - [a question or direction worth digging into deeper]
    

Read the full file on GitHub · 100 lines

Changes

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.

  1. 13d ago Changed 840b19e47e69
  2. 22d ago Changed 3716406d47a9
  3. 1mo ago Changed fa6472fde350
  4. 1mo ago First seen · 100 lines · 0 tokens per session scan A 7c3101ad2436

Subscribe to this mod's changes

wiki-discover is a command published in the GitHub repository alfadur7/llm-wiki-newsroom (173 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,571 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.

Related

Other commands, from other repositories

slm-remember

Capture durable facts, decisions, constraints, and gotchas into SuperLocalMemory. Use when the user says "remember that", "save this decision", "note this constraint", or when a session produces a conclusion worth persisting across sessions. Always recall first to avoid duplicates.

qualixar/superlocalmemory · 60 tokens

slm-media

Save pictures and PDFs in SuperLocalMemory and find them again by describing them. Covers when to save a picture or document, remembermedia, rememberdocument, getmedia, mediastatus and mediauploadlink, how recall returns pictures and PDF pages, the limits, what stays private, turning the feature on with slm media (16…

qualixar/superlocalmemory · 101 tokens

slm-session

Manage SuperLocalMemory session lifecycle — call sessioninit once at the start of every fresh session to load relevant project context and get a sessionid; call closesession when work is meaningfully complete to commit temporal summaries. Correct lifecycle hygiene is what makes SLM's learning loop work.

qualixar/superlocalmemory · 60 tokens

slm-status

Health and optimization stats for SuperLocalMemory — call slmoptimizestats() for live compression and cache counters (compressruns, tokenssavedcompress, cacheproxyhits, cacheproxymisses, cachekvhits, cachekvmisses); run slm status [--json] for system state (mode, profile, DB size, fact/entity/edge counts) and slm…

qualixar/superlocalmemory · 112 tokens

slm-bot-memory

Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Explains agentid attribution vs. profile/scope access, how to namespace by agentid + profile + scope, and what must never be written to memory. Read this before the first remember/recall on a new…

qualixar/superlocalmemory · 82 tokens

slm-getting-started-bot

First-session orientation for SuperLocalMemory on a headless bot host (Grok Bot, or any Cursor-format plugin install with no hooks, no dashboard, and no interactive setup wizard). What is different here vs. Claude Code/Codex, which 19 tools are actually available, and the first three calls to make.

qualixar/superlocalmemory · 74 tokens