A codebase exploration command that investigates a development task through several focused searches and combines the findings. It reports the relevant architecture, files, reusable parts, and an implementation approach.

Use it when you need to understand an unfamiliar repository before making a change, such as adding a page, route, form, or feature.

It avoids starting implementation before understanding how the project is organised. Parallel investigation can reveal existing routes, components, data handling, and project constraints together.

How ikhanux/ai-coding-blueprint configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ikhanux/ai-coding-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ikhanux/ai-coding-blueprint/main/.claude/commands/explore.md

Clone the repo

git clone --depth 1 https://github.com/ikhanux/ai-coding-blueprint

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ikhanux/ai-coding-blueprint/explore/github.svg)](https://agentmods.dev/commands/ikhanux/ai-coding-blueprint/explore)

Your own site

<a href="https://agentmods.dev/commands/ikhanux/ai-coding-blueprint/explore"><img src="https://agentmods.dev/badge/commands/ikhanux/ai-coding-blueprint/explore/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ikhanux/ai-coding-blueprint/explore"><img src="https://agentmods.dev/badge/commands/ikhanux/ai-coding-blueprint/explore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 197 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What 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.1	$0.00015	$0.00197
Opus 5.5	$0.00006	$0.00079
Sonnet 5.5	$0.00003	$0.00039
Haiku 4.5	$0.00002	$0.00020

Measured 1mo ago against content hash 371125eb73ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

explore 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 1mo 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.

.claude/commands/explore.md · 22 lines

What it actually says

Your task

Explore the codebase to understand: $ARGUMENTS

Break this into 2-4 focused sub-tasks and investigate each in parallel using Explore agents.

Example: "add a settings page"

Find the existing page + route registration pattern (where pages live, how they're wired)
Find the shared components already available that the page can reuse
Find how existing pages get their data and how forms are handled
Check .ai/PROJECT.md for the feature area, actors, and any cuts that constrain the feature

Run all explorations in parallel, then synthesise findings into:

Current architecture overview (only what's relevant to the task)
Files to modify and files to create
What can be reused vs. what needs to be built
Recommended implementation approach

Changes

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.

1mo ago First seen · 22 lines · 15 tokens per session scan A 371125eb73ab

Subscribe to this mod's changes

explore is a command published in the GitHub repository ikhanux/ai-coding-blueprint (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 197 once invoked, about $0.0001 per session on Opus 5.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-09-21.

Planning

explore next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
exploreikhanux/ai-coding-blueprint	Command	2	1mo ago	MIT	A	15	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

ai-coding-blueprint: Command for Claude Code