explore-codebase

explore-codebase is a skill for Claude Code from JimmyPaolini/codebase. It costs 82 tokens per session (470 once invoked), scanned A, original, MIT.

A codebase research guide that finds relevant files, coding patterns, project dependencies, and related plans for a specific topic.

In plain words
What is it for?
Use it to gather implementation context, identify affected Nx projects, and report reusable code and existing conventions without making changes.
Why use it?
It removes the need to search through an unfamiliar repository manually before planning or changing code.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; installed under .agents/ (shared by several agents); mentions AGENTS.md.

Good fit Use it to gather implementation context, identify affected Nx projects, and report reusable code and existing conventions without making changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jimmypaolini/codebase/explore-codebase
Install

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.

Any agent
npx skills add JimmyPaolini/codebase --skill explore-codebase
Clone the repo
git clone --depth 1 https://github.com/JimmyPaolini/codebase

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.

agentmods badge for explore-codebase

README.md
[![agentmods](https://agentmods.dev/badge/skills/jimmypaolini/codebase/explore-codebase/github.svg)](https://agentmods.dev/skills/jimmypaolini/codebase/explore-codebase)
Your own site
<a href="https://agentmods.dev/skills/jimmypaolini/codebase/explore-codebase"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/explore-codebase/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.

agentmods 80×15 button for explore-codebase

Your own site · 80×15
<a href="https://agentmods.dev/skills/jimmypaolini/codebase/explore-codebase"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/explore-codebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 470 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.00470
Opus 5.5 $0.00033 $0.00188
Sonnet 5.5 $0.00016 $0.00094
Haiku 4.5 $0.00008 $0.00047

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

Security

Grade A, and why

explore-codebase 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.

.agents/skills/explore-codebase/SKILL.md · 46 lines

What it actually says

Explore Files

You are a codebase researcher. Your task is to gather detailed information about this codebase for the given topic. Do NOT implement anything — only gather and report information.

Topic: ${input:Topic}

Steps

  1. Read all AGENTS.md files: root AGENTS.md, and any in applications/, packages/, infrastructure/, tools/
  2. Search for files relevant to the topic — look for related source files, tests, configs, and scripts
  3. Read the most relevant source files to understand existing patterns (max 10 files)
  4. Check nx.json and affected project.json files for task targets, caching config, and project dependencies
  5. Search documentation/planning/ for any existing plans covering related work

Output

Return a structured Codebase Research Summary:

  • Relevant Files: list of files most relevant to the task (with brief description of each)
  • Existing Patterns: conventions and patterns already established that the plan must follow
  • Affected Projects: Nx projects likely affected
  • Reusable Code: existing utilities, helpers, or abstractions to leverage
  • Related Plans: any existing planning documents covering adjacent work
  • Constraints Discovered: hard constraints from AGENTS.md, linting, typing, or CI configuration
  • Open Questions: ambiguities that need user clarification
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.

  1. 1mo ago First seen · 46 lines · 82 tokens per session scan A 1781e686a876

Subscribe to this mod's changes

explore-codebase is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed 19d ago), licensed MIT. It adds 82 tokens to every session and 470 once invoked, about $0.0003 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-01.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens