What is codebase-locator?

A codebase search helper that finds the files, folders, and components related to a requested feature. It groups the results by purpose, such as implementation, tests, configuration, documentation, and types.

Use it to locate code for a feature, find related tests or configuration, and map the relevant parts of a repository before editing.

It reduces the time spent searching through an unfamiliar project and helps identify where a change belongs.

codebase-locator — Agent for coding agents by juicesharp: A codebase search helper that finds the files, folders…

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.

agentmods

npx agentmods add agents/juicesharp/rpiv-pi/codebase-locator

Clone the repo

git clone --depth 1 https://github.com/juicesharp/rpiv-pi

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/agents/juicesharp/rpiv-pi/codebase-locator.svg)](https://agentmods.dev/agents/juicesharp/rpiv-pi/codebase-locator)

Your own site

<a href="https://agentmods.dev/agents/juicesharp/rpiv-pi/codebase-locator"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-pi/codebase-locator.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 findings. Scan, not verified.

Origin 89% copy Near-identical to another mod 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	$0.00066	$0.00978
Opus 5	$0.00033	$0.00489
Sonnet 5	$0.00013	$0.00196
Haiku 4.5	$0.00007	$0.00098

Measured 3d ago against content hash 0e32795dacfe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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

This is a copy

89% identical to code-locator — 46 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/codebase-locator.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 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.

Core Responsibilities

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.)
Categorize Findings
- Implementation files (core logic)
- Test files (unit, integration, e2e)
- Configuration files
- Documentation files
- Type definitions/interfaces
- Examples/samples
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

Start with using your grep tool for finding keywords.
Optionally, use glob for file patterns
LS and find your way to victory as well!

Refine by Language/Framework

JavaScript/TypeScript: Look in src/, lib/, components/, pages/, api/
C#/.NET: Look in src/, Controllers/, Models/, Services/, Views/, Areas/, Data/, Entities/, Infrastructure/, Application/, Domain/, Core/
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 :)

Common Patterns to Find

*service*, *handler*, *controller* - Business logic
*test*, *spec* - Test files
*.config.*, *rc* - Configuration
*.d.ts, *.types.* - Type definitions
README*, *.md in feature dirs - Documentation

Output Format

Structure your findings like this:

## File Locations for [Feature/Topic]

### Implementation Files
- `src/services/feature.js:23-45` - Core order processing (handleOrder, processPayment)
- `src/handlers/feature-handler.js:12` - Request handling entry point
- `src/models/feature.js:8-30` - Data models (Order, LineItem)

### Test Files
- `src/services/__tests__/feature.test.js:15` - Service tests (12 cases)
- `e2e/feature.spec.js:1` - End-to-end tests

### Configuration
- `config/feature.json:1` - Feature-specific config
- `.featurerc:3` - Runtime configuration

### Type Definitions
- `types/feature.d.ts:10-25` - TypeScript definitions (OrderInput, OrderResult)

### Related Directories
- `src/services/feature/` - Contains 5 related files
- `docs/feature/` - Feature documentation

### Entry Points
- `src/index.js:23` - Imports feature module
- `api/routes.js:41-48` - Registers feature routes

Read the full file on GitHub · 108 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.

3d ago First seen · 108 lines · 66 tokens per session scan A 0e32795dacfe

Subscribe to this mod's changes

codebase-locator is an agent published in the GitHub repository juicesharp/rpiv-pi (11 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 978 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to code-locator, differing in 46 lines, and is treated as a copy.

Debugging

codebase-locator

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Core Responsibilities

Search Strategy

Initial Broad Search

Refine by Language/Framework

Common Patterns to Find

Output Format

What this file has done since we first saw it

Other agents, from other repositories

Demonstrate

playwright-test-generator

analyzer

grader

comparator

.NET-Notebook-Migration-Agent