llm-wiki-agent: Skill for Claude Code

.agents/skills/wiki-graph/SKILL.md

wiki-graph is a skill for Claude Code, Codex from regexp-lin/llm-wiki-agent. It costs 57 tokens per session (422 once invoked), scanned A, original, MIT.

A workflow that builds a knowledge graph, a visual map of pages and their relationships, from wiki files.

In plain words
What is it for?
Use it to extract links, infer additional connections, group related pages into communities, and generate graph data and an interactive visualization.
Why use it?
It helps reveal connections that are explicit in page links or inferred from page content, while marking uncertain relationships.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is regexp-lin/llm-wiki-agent's own configuration. It tells Claude Code and Codex how to work on llm-wiki-agent 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-agent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to regexp-lin/llm-wiki-agent. 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/regexp-lin/llm-wiki-agent/main/.agents/skills/wiki-graph/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/regexp-lin/llm-wiki-agent

Made for: Claude Code, Codex.

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-graph

README.md
[![agentmods](https://agentmods.dev/badge/skills/regexp-lin/llm-wiki-agent/wiki-graph/github.svg)](https://agentmods.dev/skills/regexp-lin/llm-wiki-agent/wiki-graph)
Your own site
<a href="https://agentmods.dev/skills/regexp-lin/llm-wiki-agent/wiki-graph"><img src="https://agentmods.dev/badge/skills/regexp-lin/llm-wiki-agent/wiki-graph/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-graph

Your own site · 80×15
<a href="https://agentmods.dev/skills/regexp-lin/llm-wiki-agent/wiki-graph"><img src="https://agentmods.dev/badge/skills/regexp-lin/llm-wiki-agent/wiki-graph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 422 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.00057 $0.00422
Opus 5 $0.00028 $0.00211
Sonnet 5 $0.00011 $0.00084
Haiku 4.5 $0.00006 $0.00042

Measured 9d ago against content hash 0f9e16ac63ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

wiki-graph 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 9d 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.

.agents/skills/wiki-graph/SKILL.md · 52 lines

What it actually says

Wiki Graph

Build a knowledge graph from wiki page relationships.

Triggers

  • build graph / build the knowledge graph
  • "构建图谱" / "知识图谱"

Steps

  1. Collect all wiki pages
  2. Pass 1 — Extract: Parse all [[wikilinks]] → EXTRACTED edges (zero API)
  3. Pass 2 — Infer (optional): SHA256 diff → changed pages → Claude API → INFERRED / AMBIGUOUS edges
  4. Community Detection: Louvain algorithm → community IDs + colors
  5. Output graph/graph.json + graph/graph.html (vis.js)
  6. Update graph/.cache.json
  7. Append wiki/log.md

Edge Types

Type Source Color
EXTRACTED [[wikilinks]] #555555
INFERRED Semantic, high confidence #FF5722
AMBIGUOUS Semantic, low confidence #BDBDBD

Node Type Colors

Type Color
source Green (#4CAF50)
entity Blue (#2196F3)
concept Orange (#FF9800)
synthesis Purple (#9C27B0)
unknown Gray (#9E9E9E)

CLI Fallback

If Node.js available: pnpm dev:graph Otherwise: build graph data manually using Grep + Read tools.

For detailed execution flow, read .cursor/skills/wiki-graph/workflow-detail.md.

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 52 lines · 57 tokens per session scan A 0f9e16ac63ab

Subscribe to this mod's changes

wiki-graph is a skill published in the GitHub repository regexp-lin/llm-wiki-agent (15 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 422 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens