navgator
Architecture tracking — map dependencies, analyze impact, and visualize your stack before making changes
By Tyrone RossLicense: Apache-2.00 GitHub starsUpdated 3 weeks ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 6 skill or MCP entries
- Source updated
- Sep 29, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install navgator for Codex and Claude Code
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add navgator@agent-plugin-marketplacePaste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/tyroneross/NavGatorClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/architecture-export/SKILL.md├── skills/architecture-scan/SKILL.md├── skills/code-review/SKILL.md├── skills/impact-analysis/SKILL.md├── skills/infrastructure-scanning/SKILL.md└── skills/navgator-setup/SKILL.md
Included Skills6
Use when user asks to show or generate an architecture diagram, visualize dependencies, export architecture docs, create architecture documentation, save architecture output, or create a mermaid diagram of their project.
Use when user asks to scan architecture, check dependencies, find outdated packages, show project structure, refresh architecture, or run a health check. Navgator scan, status, and staleness check.
Architectural integrity review of changes already made — system flow, connections, drift. Use when user asks to review architecture, check connections, navgator review, is this safe to merge, what did I break, or when scan detects architectural drift. Not for forecasting the effect of a change you have not made yet; use `impact-analysis` instead.
Forecasts the blast radius of a change before you make it — dependencies, connections, data flow. Use when user asks what breaks if I change X, impact of changing, what depends on, trace data flow, show connections, dependency graph, upstream/downstream, or safe to modify before refactoring. Not for reviewing changes already made; use `code-review` instead.
Detects and analyzes infrastructure components — Prisma models, env vars, queues, crons, deploy configs, field usage, type validation. Use when user asks about database schema/models, environment variables, queue or cron setup, deploy config, or whether Prisma types match TypeScript. Not for general package/dependency health; use `architecture-scan` instead.
Use when user asks to install navgator, update navgator, set up navgator, launch the dashboard, or run navgator ui maintenance.
Plugin manifests2
{
"name": "navgator",
"description": "Architecture tracking — map dependencies, analyze impact, and visualize your stack before making changes",
"author": {
"name": "Tyrone Ross",
"url": "https://github.com/tyroneross"
},
"homepage": "https://github.com/tyroneross/NavGator",
"repository": "https://github.com/tyroneross/NavGator",
"license": "Apache-2.0",
"keywords": [
"architecture",
"connections",
"context",
"dependencies",
"impact-analysis"
],
"skills": "./skills",
"interface": {
"displayName": "NavGator",
"shortDescription": "Architecture tracking — map dependencies, analyze impact, and visualize your stack before making changes",
"longDescription": "Architecture tracking — map dependencies, analyze impact, and visualize your stack before making changes",
"developerName": "Ross Labs",
"category": "Coding",
"capabilities": [
"Read",
"Write"
]
}
}{
"name": "navgator",
"description": "Map dependencies and analyze blast radius before changing code",
"author": {
"name": "Tyrone Ross",
"url": "https://github.com/tyroneross"
},
"homepage": "https://github.com/tyroneross/NavGator",
"repository": "https://github.com/tyroneross/NavGator",
"license": "Apache-2.0",
"keywords": [
"architecture",
"connections",
"context",
"dependencies",
"impact-analysis"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[navgator on Agent Plugins Marketplace](https://pluginsmp.com/plugins/navgator)