Claude Code plugins from Anthony Maio for repo intelligence and agent workflows.
npx claudepluginhub anthony-maio/cartographRepo analysis for coding agents with slash commands, skills, documentation agents, and a bundled Cartograph MCP server.
Cartograph is task-shaped repo context for coding agents. It ships a CLI, an MCP server, user-scope install adapters for Claude Code and OpenClaw, and packaged agent assets for documentation-heavy workflows.
@anthony-maio/cartographio.github.anthony-maio/cartographcartograph.making-minds.aiInstead of dumping an entire repository into context, Cartograph ranks the files that matter, maps dependencies, caches structured artifacts, and lets the next tool or agent pick up from those artifacts.
The primary workflow is:
analyze to map the repopacket to prepare the workcontext to load the minimum fileswiki, host installs, and benchmarks are secondary surfaces built around that core path.
npm install
npm run build
For global use from npm:
npm install -g @anthony-maio/cartograph
For MCP host discovery via the official registry:
io.github.anthony-maio/cartographFor Claude Code plugin install from this public repo:
/plugin marketplace add anthony-maio/cartograph
/plugin install cartograph@making-minds-tools
For global use from a local checkout:
npm install -g .
See CONTRIBUTING.md for the development workflow and SECURITY.md for vulnerability reporting.
This repo also acts as a Claude Code plugin marketplace. The cartograph plugin bundles:
/cartograph:analyze, /cartograph:context, /cartograph:wikiuse-cartograph and repo-surveyor skillsrepo-scout, dependency-tracer, context-picker, api-surface-writer, and wiki-writerInstall it with:
/plugin marketplace add anthony-maio/cartograph
/plugin install cartograph@making-minds-tools
If you only remember one thing, remember this:
cartograph analyze <repo> --static
cartograph packet <repo> --type <type> --task "<task>"
cartograph context <repo> --task "<task>" --json
analyze maps the repo and tells you what matters.packet turns a concrete job into a reusable working artifact.context gives the next agent the smallest useful file set.cartograph analyze <repo> [options]
cartograph packet <repo> --type <type> --task "<task>" [--changed <paths...>]
cartograph context <repo> --task "<task>" [options]
cartograph wiki <repo> [options]
cartograph export <run-id> --to <path> [--artifact <name>]
cartograph install <claude|openclaw|mcp>
cartograph uninstall <claude|openclaw|mcp>
cartograph doctor [target] [--json]
cartograph mcp
Legacy compatibility still works:
cartograph <repo> --static
cartograph <repo> -c "trace auth flow"
# Map the repo
cartograph analyze ./my-project --static
# Prepare a concrete job
cartograph packet ./my-project --type bug-fix --task "fix auth refresh bug" --changed src/auth/service.ts tests/auth/service.test.ts
# Load the minimum file set for that job
cartograph context ./my-project --task "add user authentication" --json
# Force embedded snippets when you really want them
cartograph analyze ./my-project --static --json --include-contents
# Full wiki output
cartograph wiki ./my-project -p gemini -k $CARTOGRAPH_API_KEY -o wiki.md
# Export a cached artifact to an explicit path
cartograph export run-abc123 --to ./artifacts/wiki.md
# Run the MCP server directly
cartograph mcp
For small repos, analyze --static --json now defaults to compact output instead of embedding top-file contents. That keeps tiny repos readable and lets direct file reads stay cheaper than a giant JSON blob. Use --include-contents when you explicitly want embedded snippets.
The default markdown output from analyze --static is human-first: it highlights what matters, surfaces dependency hubs, and recommends the next commands instead of dumping raw file contents immediately.
geminiopenaiopenrouterollamaSet the API key with --key or CARTOGRAPH_API_KEY. Ollama does not require a key.
Cartograph writes successful runs into the user cache by default:
%USERPROFILE%\\.cartograph\\cache~/.cartograph/cacheEach run gets a manifest plus named artifacts, which keeps agent handoffs lightweight and makes cartograph export deterministic.
Cartograph uses an explicit hybrid install model. Installing the package does not modify Claude Code, OpenClaw, or MCP host configs automatically.
Production-ready workflow orchestration with 84 marketplace plugins, 192 local specialized agents, and 156 local skills - optimized for granular installation and minimal token usage
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations
Curated collection of 154 specialized Claude Code subagents organized into 10 focused categories