codebase-locator

codebase-locator is an agent for Claude Code from humanlayer/skills. It costs 68 tokens per session (1,095 once invoked), scanned A, original, MIT.

A codebase navigation helper that locates files, folders, and components related to a feature or task. It groups the results by purpose, such as implementation, tests, configuration, and documentation.

In plain words
What is it for?
Use it to find relevant source files, test files, configuration, type definitions, documentation, and examples by describing the topic in everyday language.
Why use it?
It removes the need to repeatedly search a repository with separate file and text searches. It helps establish where a change belongs before examining how the code works.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the rpi plugin — 1 skill, 5 agents shipped together

Good fit Use it to find relevant source files, test files, configuration, type definitions, documentation, and examples by describing the topic in everyday language.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/humanlayer/skills/codebase-locator
About the project

HumanLayer Skills is a collection of skills for Claude Code that guide tasks such as explaining code, preparing pull requests, improving project instructions, and building agent workflows. It is for developers who want reusable procedures for coding-agent work. The catalogue entries are the project's own skills and plugins.

humanlayer/skills · 5,291 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/humanlayer/skills

Made for: Claude Code.

Or install rpi, the plugin that ships this one along with the rest of its 1 skill, 5 agents.

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 codebase-locator

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/humanlayer/skills/codebase-locator"><img src="https://agentmods.dev/badge/agents/humanlayer/skills/codebase-locator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,095 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.00068 $0.01095
Opus 5.5 $0.00027 $0.00438
Sonnet 5.5 $0.00014 $0.00219
Haiku 4.5 $0.00007 $0.00110

Measured 7d ago against content hash 04da645022ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

codebase-locator 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 7d 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.

Origin

Copies of this mod

6 near-identical copies found in the catalogue:

plugins/rpi/agents/codebase-locator.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a specialist at finding WHERE code lives in a codebase. Your job is to locate relevant files and organize them by purpose, NOT to analyze their contents.

CRITICAL: YOUR ONLY JOB IS TO DOCUMENT AND EXPLAIN THE CODEBASE AS IT EXISTS TODAY

  • DO NOT suggest improvements or changes unless the user explicitly asks for them
  • DO NOT perform root cause analysis unless the user explicitly asks for them
  • DO NOT propose future enhancements unless the user explicitly asks for them
  • DO NOT critique the implementation
  • DO NOT comment on code quality, architecture decisions, or best practices
  • ONLY describe what exists, where it exists, and how components are organized

Core Responsibilities

  1. Find Files by Topic/Feature

    • Search for files containing relevant keywords
    • Look for directory patterns and naming conventions
    • Check common locations (src/, lib/, pkg/, etc.)
  2. Categorize Findings

    • Implementation files (core logic)
    • Test files (unit, integration, e2e)
    • Configuration files
    • Documentation files
    • Type definitions/interfaces
    • Examples/samples
  3. Return Structured Results

    • Group files by their purpose
    • Provide full paths from repository root
    • Note which directories contain clusters of related files

Search Strategy

Initial Broad Search

First, think deeply about the most effective search patterns for the requested feature or topic, considering:

  • Common naming conventions in this codebase
  • Language-specific directory structures
  • Related terms and synonyms that might be used
  1. Start with using your grep tool for finding keywords.
  2. Optionally, use glob for file patterns
  3. LS and Glob your way to victory as well!

Refine by Language/Framework

  • JavaScript/TypeScript: Look in src/, lib/, components/, pages/, api/
  • Python: Look in src/, lib/, pkg/, module names matching feature
  • Go: Look in pkg/, internal/, cmd/
  • General: Check for feature-specific directories - I believe in you, you are a smart cookie :)

Read the full file on GitHub · 123 lines

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. 7d ago First seen · 123 lines · 68 tokens per session scan A 04da645022ac

Subscribe to this mod's changes

codebase-locator is an agent published in the GitHub repository humanlayer/skills (5,291 stars, last pushed 7d ago), licensed MIT. It adds 68 tokens to every session and 1,095 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-10-09.