Map

NEO — Claude Code plugin: Matrix-themed 11-agent orchestrator with a second brain that never forgets

Install

npx -y skills add vidit19sharma/neogents --skill map

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Deep codebase mapping. Fans out parallel keymaker recon across an existing repository and has neo-shadow synthesize the findings into ARCHITECTURE.md. Use when adopting NEO in a mature codebase, when ARCHITECTURE.md is empty or stale, or when the user asks to map or document the codebase structure.

SKILL.md

2.2 KB, 476 tokens by cl100k_base, as published. Nobody here has run it

Build or refresh the second brain's map of this codebase.

Current state

Brain: !ls .neo/brain 2>/dev/null || echo "MISSING"
ARCHITECTURE.md size: !wc -l .neo/brain/ARCHITECTURE.md 2>/dev/null || echo "n/a"
Graphify: !command -v graphify >/dev/null 2>&1 && echo "available" || echo "not installed"

Steps

Guard. No .neo/brain/ → stop and suggest /neo:init first. This command fills the map; init builds the shelf.
Recon fan-out. Spawn keymakers IN PARALLEL (one message, 3–4 spawns), each with the full 6-section contract and ONE angle:
- Stack & entry points: languages, frameworks + versions from manifests, build/test/lint commands, where execution starts.
- Layout & boundaries: top-level modules, what owns what, how layers talk (imports, APIs, events).
- Patterns & conventions: error handling, naming, state management, test conventions — concrete one-liners with file:line examples.
- Gotchas & hotspots: the biggest files, circular-looking dependencies, anything where "X looks like Y but is actually Z".
If graphify is available and a graph.json exists, tell each keymaker to prefer graphify query/path/explain over broad grep.
Synthesize via shadow. Spawn neo-shadow with ALL recon findings as the delta. Contract: rewrite ARCHITECTURE.md (Stack / Layout / Patterns / Gotchas — concrete, file-anchored, no prose padding); extract any subsystem too big for a section into .neo/brain/topics/<name>.md and [[wiki-link]] it; update INDEX.md pointers; touch nothing else.
Report. Tell the user what the map now covers, its size (flag if ARCHITECTURE.md pushed past ~500 lines — shadow should have split topics), and anything the recon flagged as unclear or contradictory.

Re-running is safe: shadow rewrites from current findings, and prior knowledge lives in git history.

What ships with it

Read from the repository