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.
git clone --depth 1 https://github.com/juicesharp/rpiv-piWrote 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.
[](https://agentmods.dev/agents/juicesharp/rpiv-pi/codebase-locator)<a href="https://agentmods.dev/agents/juicesharp/rpiv-pi/codebase-locator"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-pi/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.
<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="Reviewed on agentmods" width="80" height="20"></a>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.00066 | $0.00978 |
| Opus 5.5 | $0.00026 | $0.00391 |
| Sonnet 5.5 | $0.00013 | $0.00196 |
| Haiku 4.5 | $0.00007 | $0.00098 |
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 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- codebase-locator — 89% identical, 49 lines differ
- codebase-locator — 86% identical, 42 lines differ
- codebase-locator — 86% identical, 31 lines differ
- codebase-locator — 83% identical, 50 lines differ
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 definitionsREADME*,*.mdin 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
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 · 108 lines · 66 tokens per session scan A 0e32795dacfe
codebase-locator is an agent published in the GitHub repository juicesharp/rpiv-pi (14 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 978 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-08-30.
Other agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…