# knowledge-mapper

knowledge-mapper turns a subject into a map of concepts: nodes, typed links, clusters and routes between ideas. Handy when a topic is too big to keep in your head at once.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 1357 repo stars
- Author: qdhenry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/agents/wfgy/knowledge-mapper.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/knowledge-mapper

## What it does

Every concept becomes a node carrying a domain, an importance weight and coordinates. Links between nodes get a type and a strength; the types run from `is-a` and `part-of` to `causes`, `requires`, `opposite-of` and `leads-to`. Groups of related nodes become clusters with a centroid and a coherence score.

You drive it with starred commands: `*build-graph` reads the current context, `*map-connections` lists what a concept touches, `*trace-path` connects two ideas, `*find-gaps` reports empty areas, `*export-graph` writes the result out. Activation runs `/semantic:tree-init`, loads stored maps from `.wfgy/maps/`, then prints `*help`. The agent runs on sonnet and can read, write and search files, run Bash, and fetch pages from the web.

Helper commands live in `.claude/commands/semantic/` and `.claude/commands/reasoning/`. Skip them and activation's init step has nothing to call, because `/semantic:tree-init` resolves to a file in that first folder. The agent itself is one file: `.claude/agents/knowledge-mapper.md`.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/knowledge-mapper.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/knowledge-mapper.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/knowledge-mapper.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/agents/wfgy/knowledge-mapper.md

## When to use it
- split a sprawling topic into nodes and links
- trace a route between two concepts
- lay out a study order for an unfamiliar field
- spot which parts of a knowledge map stay empty
- export a concept graph for a write-up

## Example prompts
- Map the concepts in this spec: run `*build-graph`, then `*visualize-map`.
- How do `transactions` and `isolation levels` connect? Use `*trace-path`.
- Run `*find-gaps` over my notes and tell me what's missing.

## Similar
- [team-knowledge-mapper](https://affpapa.org/en/nevibecode/commands/team-knowledge-mapper.md) — command · 235 installs
- [knowledge-graph](https://affpapa.org/en/nevibecode/skills/knowledge-graph.md) — skill · ★ 239 repo stars
- [agent-knowledge](https://affpapa.org/en/nevibecode/mcp/agent-knowledge.md) — MCP server · ★ 19 repo stars
- [vault-knowledge](https://affpapa.org/en/nevibecode/mcp/vault-knowledge.md) — MCP server
- [obsidian-visualize](https://affpapa.org/en/nevibecode/commands/obsidian-visualize.md) — command · ★ 5412 repo stars
- [temple-generator](https://affpapa.org/en/nevibecode/skills/temple-generator.md) — skill · 199 installs

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
