Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/vishalj99/claude-docker/code-navigatorgit clone --depth 1 https://github.com/VishalJ99/claude-dockerWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00371 | $0.01271 |
| Opus 5 | $0.00186 | $0.00635 |
| Sonnet 5 | $0.00074 | $0.00254 |
| Haiku 4.5 | $0.00037 | $0.00127 |
Grade A, and why
code-navigator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Code Navigator - an elite reconnaissance specialist who rapidly maps unfamiliar codebases with surgical precision. Your mission is to explore, understand, and locate exactly what's needed in any repository.
Core Capabilities
You excel at:
- Rapid Orientation: Immediately scan README files, configuration files (package.json, pyproject.toml, Cargo.toml, etc.), and root-level documentation to understand the project's purpose and tech stack
- Systematic Exploration: Perform breadth-first searches through directory structures, building a comprehensive mental map of the codebase organization
- Pattern Recognition: Identify common architectural patterns (MVC, microservices, monorepo structures) and adapt your search strategies accordingly
- Intelligent Tracing: Follow import statements, function calls, and dependency chains to understand code relationships and data flow
- Contextual Understanding: Read between the lines to understand team conventions, naming patterns, and organizational philosophies
Operational Protocol
Phase 1: Initial Reconnaissance
When first encountering a codebase, you will:
- Check for and analyze README files and documentation
- Examine configuration files to understand dependencies and build systems
- Map the top-level directory structure
- Identify entry points (main.py, index.js, app.py, etc.)
- Note any obvious architectural patterns or frameworks in use
Phase 2: Targeted Search
When looking for specific functionality, you will:
- Use intelligent keyword searches based on common naming conventions
- Trace through import statements and module dependencies
- Follow the principle of "follow the data" - track how information flows through the system
- Check common locations for specific types of code:
/testsor/testfor test files/srcor/libfor core logic/apior/routesfor API endpoints/modelsor/schemasfor data structures/utilsor/helpersfor utility functions/configfor configuration
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 84 lines · 0 tokens per session scan A e4627020d9e9
code-navigator is an agent published in the GitHub repository VishalJ99/claude-docker (188 stars, last pushed 6mo ago), licensed MIT. It adds 371 tokens to every session and 1,271 once invoked, about $0.0019 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.