Orient Tools

Understand the codebase before changing it. All Orient tools are free.

pharaoh_recon

Question it answers: "What do I need to know about this codebase before starting work?"

Batched reconnaissance — runs codebase map, module context, function search, and blast radius queries in parallel, server-side, in a single call. Designed for the start of any task that needs multiple pieces of context at once.

When to use: Starting a new task, running a plan review, PR review, or architecture assessment.

Parameters:

• repo (required): Repository name

• include_map (optional): Include codebase map (default: true)

• modules (optional): Module names to get context for (max 5)

• functions (optional): Function search queries (max 3)

• blast_radius (optional): Blast radius targets (max 3)

• dependencies (optional): Module dependency pairs to trace (max 3)

get_codebase_map

Question it answers: "What modules exist and how do they relate?"

Returns all modules with file counts and lines of code, the dependency graph with weights and bidirectional warnings, hot files (most changed in the last 90 days), and all HTTP endpoints with their handler files.

When to use: Starting any new conversation. This is the first call — always.

Parameters:

• repo (required): Repository name

• include_metrics (optional): Include LOC, complexity, change frequency

get_module_context

Question it answers: "What does this module look like before I modify it?"

Returns the complete module profile in ~2K tokens: file count, LOC, all exported function signatures with complexity, dependency graph (imports from + imported by), DB table access, HTTP endpoints, cron jobs, env vars, vision spec alignment, and external callers from other modules.

When to use: Before modifying code in a module, writing a PRD, or checking what depends on a module.

Parameters:

• repo (required): Repository name

• module (required): Module name (e.g., "auth", "db", "mcp")

search_functions

Question it answers: "Does this already exist somewhere?"

Searches all functions across the entire codebase by name or partial match. Returns file paths, line numbers, module, export status, async flag, complexity scores, and full signatures.

When to use: Before creating any new function. Search first, import if it exists.

Parameters:

• repo (required): Repository name

• query (required): Function name or partial match

• module (optional): Filter to a specific module

• exported_only (optional): Only show exported functions

get_design_system

Question it answers: "What UI components and tokens already exist?"

Discovers design system components, color tokens, typography scales, spacing values, and common anti-patterns in the codebase.

When to use: Before creating any UI component. Check what already exists and follow established patterns.

Parameters:

• repo (required): Repository name