explaingit

oil-oil/codex-explore-skill

11UnknownAudience · developerComplexity · 2/5ActiveLicenseSetup · easy

TLDR

A Codex skill that delegates codebase reconnaissance to explorer subagents before any edits, so the main agent gets a key-files summary instead of raw source.

Mindmap

mindmap
  root((codex-explore-skill))
    Inputs
      $explore keyword
      Target codebase
    Outputs
      Key files table
      Reconnaissance summary
      Read suggestions
    Use Cases
      Onboard new repos
      Plan large refactors
      Reduce context noise
    Tech Stack
      Codex
      Shell
      Markdown

Things people build with this

USE CASE 1

Map an unfamiliar codebase before letting Codex edit it

USE CASE 2

Force Codex to produce a key-files table before planning changes

USE CASE 3

Categorize files as primary, legacy, or generated during agent exploration

USE CASE 4

Speed up Codex sessions on large repos by offloading reads to subagents

Tech stack

CodexShellMarkdown

Getting it running

Difficulty · easy Time to first run · 5min

Just clone into ~/.codex/skills/explore and reference $explore in prompts.

MIT, very permissive, lets you reuse the code for almost anything as long as you keep the copyright notice.

In plain English

This is a small add-on for Codex, an AI coding assistant. The add-on is called a skill, which is a piece of behaviour you can plug into Codex so the assistant follows specific rules when a particular keyword is mentioned in the conversation. This particular skill is named Explore. The job of Explore is to make Codex stop and look around before it starts changing code. When a developer is about to ask Codex to work on a project, especially one Codex has not seen before, it can be slow and noisy if the main assistant reads dozens of files itself. Instead, the Explore skill tells Codex to first hand the reconnaissance work off to smaller helper agents called explorer subagents. Those helpers read the project, take notes, and report back a short summary plus a table of the most important files and suggestions for what to read next. The main conversation can then concentrate on planning the actual change instead of being filled up with raw source code. Installing the skill is one shell command: clone the repository into the ~/.codex/skills/explore folder. After that, the user mentions $explore in a Codex prompt, for example "Use $explore to map this codebase before making changes," and the skill takes over. The README lists the rules the skill enforces. The main agent is not allowed to read the target codebase while the explorer subagents are still working. Before any large local reading or editing begins, a key-files table must exist. The explorers are asked to label files as primary, legacy, experimental, generated, unused, or unclear when they can tell, and to group likely changes by concern such as user interface, API, state management, data model, permissions, internationalisation, tests, or configuration. The project is released under the MIT licence. The README is short and does not list a programming language or any additional configuration options.

Copy-paste prompts

Prompt 1
Show me how to install the Explore skill into ~/.codex/skills/explore
Prompt 2
Walk me through what $explore changes in a Codex session
Prompt 3
Help me write a similar Codex skill that maps test coverage
Prompt 4
Explain the rules the Explore skill enforces on the main agent
Prompt 5
Generate a key-files table for my repo using the Explore conventions
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.