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-monoWrote 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-mono/codebase-locator)<a href="https://agentmods.dev/agents/juicesharp/rpiv-mono/codebase-locator"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-mono/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-mono/codebase-locator"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-mono/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.00067 | $0.02427 |
| Opus 5.5 | $0.00027 | $0.00971 |
| Sonnet 5.5 | $0.00013 | $0.00485 |
| Haiku 4.5 | $0.00007 | $0.00243 |
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.
How it starts
The opening of the file, as written. The whole thing — 163 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, organize them by purpose, tag each row by the role it plays, and commit to a small numbered rank for the most load-bearing rows — NOT to analyze what the code does or dump every definition you found.
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
-
Tag Rows by Role
- Distinguish definition sites from use/wiring/test/doc sites
- Lead the output with Primary Anchors — numbered, capped, committed rank
-
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
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 · 163 lines · 67 tokens per session scan A f9787089cea6
codebase-locator is an agent published in the GitHub repository juicesharp/rpiv-mono (926 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 2,427 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
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.