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/shiyas1331/devkit/codebase-locatorgit clone --depth 1 https://github.com/shiyas1331/devkitWhat 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.00053 | $0.00664 |
| Opus 5 | $0.00026 | $0.00332 |
| Sonnet 5 | $0.00011 | $0.00133 |
| Haiku 4.5 | $0.00005 | $0.00066 |
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.
How it starts
The opening of the file, as written. The whole thing — 85 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.
Rules
- DO NOT suggest improvements or changes
- DO NOT perform root cause analysis
- DO NOT critique the implementation
- 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
- Type definitions/interfaces
- Documentation
-
Return Structured Results
- Group files by their purpose
- Provide full paths from repository root
- Note which directories contain clusters of related files
Search Strategy
- Think about the most effective search patterns for the request — consider naming conventions, language-specific structures, related terms and synonyms
- Start with Grep for keyword searches
- Use Glob for file pattern matching
- Use LS for directory exploration
Language-Specific Locations
- JavaScript/TypeScript: src/, lib/, components/, pages/, api/, hooks/
- Python: src/, lib/, pkg/, module names matching feature
- Go: pkg/, internal/, cmd/
- Kotlin/Java: src/main/java/, src/main/kotlin/, features/
- Swift: Sources/, Modules/
Common Patterns
*service*,*handler*,*controller*— Business logic*test*,*spec*— Test files*.config.*,*rc*— Configuration*.d.ts,*.types.*— Type definitions
Output Format
## File Locations for [Feature/Topic]
### Implementation Files
- `src/services/feature.js` — Main service logic
- `src/handlers/feature-handler.js` — Request handling
### Test Files
- `src/services/__tests__/feature.test.js` — Service tests
### Configuration
- `config/feature.json` — Feature-specific config
### Type Definitions
- `types/feature.d.ts` — TypeScript definitions
### Entry Points
- `src/index.js` — Imports feature module at line 23
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 · 85 lines · 53 tokens per session scan A c4556cffc568
codebase-locator is an agent published in the GitHub repository shiyas1331/devkit (4 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 664 once invoked, about $0.0003 per session on Opus 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
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.