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.
npx agentmods add agents/captainme-ai/lead-dev-os/codebase-locatorgit clone --depth 1 https://github.com/CaptainMe-AI/lead-dev-osWhat 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.00068 | $0.01092 |
| Opus 5 | $0.00034 | $0.00546 |
| Sonnet 5 | $0.00014 | $0.00218 |
| Haiku 4.5 | $0.00007 | $0.00109 |
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 yesterday.
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.
This is a copy
94% identical to codebase-locator — 2 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.
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
-
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 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 :)
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.
- yesterday First seen · 123 lines · 68 tokens per session scan A 2c18e95968d1
codebase-locator is an agent published in the GitHub repository CaptainMe-AI/lead-dev-os (2 stars, last pushed 12d ago), licensed MIT. It adds 68 tokens to every session and 1,092 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to codebase-locator, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
researcher
Read-only web and registry lookup. Use for Agent Skill / MCP discovery (npx skills find, MCP search), current-usage doc-checks, and scope source verification. Returns only a compact summary, never raw pages.
scout
Read-only code exploration and repo scanning. Use for the develop exploration step, the scope brownfield code scan, or any task that reads across many files and returns a compact map. Never edits.
explorer-rag-enhanced
MUST BE USED PROACTIVELY. Universal read-only explorer agent. Combines jrag graph navigation (call chains, service boundaries, routes, impact analysis, FQN resolution) with broad file-system search (grep, glob, excerpt reading). Use for any exploration task: locating code, tracing dependencies, finding patterns…
test-audit
Audits test code for quality, structure, and patterns. Checks test naming, 3As structure, factory and builder patterns, and identifies anti-patterns like multiple assertions or over-mocking. Based on real codebase with 63 factories and 12 builders.
hydraflow-review-advisor
Advisor role in HydraFlow's self-repairing review pipeline. Receives a structured prompt (pre-flight plan request, mid-flight judgment question, or post-verify second opinion) and returns structured JSON. Routes to Opus by default per the advisor pattern. Read-only by intent: the executor handles writes.
docs-watcher
Review code/config changes and keep all docs fresh across three altitudes — internal docs (docs/DESIGN.md WHAT/WHY, docs/ARCHITECTURE.md HOW), operator docs in docs/ (CONFIGURATION, CLI, AGENT-GUIDE, CODEBASEREQUIREMENTS, MANUAL-VERIFICATION-CHECKLIST), and the consumer skills/ + agents/ artifacts deployed verbatim to…