Production-ready Model Context Protocol (MCP) server for multi-agent AI consultations (Codex, Claude, Anti-Gravity, Mimo) with Minimax-M3 consensus synthesis
Skill Claude CodeCodex
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
Skill Claude CodeCodex
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
Skill Claude CodeCodex
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow".
Skill Claude CodeCodex
Documents GitNexus itself — available tools, knowledge graph queries, MCP resources, graph schema, and workflow reference. Activated by GitNexus-related questions about tooling, usage, and capabilities.
Skill Claude CodeCodex
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
Skill Claude CodeCodex
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?".
Skill Claude CodeCodex
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".
Skill Claude CodeCodex
Production-ready Model Context Protocol (MCP) server for multi-agent AI consultations (Codex, Claude, Anti-Gravity, Mimo) with Minimax-M3 consensus synthesis.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: