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/iamironz/ai-config-bundleWrote 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/iamironz/ai-config-bundle/codebase-locator)<a href="https://agentmods.dev/agents/iamironz/ai-config-bundle/codebase-locator"><img src="https://agentmods.dev/badge/agents/iamironz/ai-config-bundle/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/iamironz/ai-config-bundle/codebase-locator"><img src="https://agentmods.dev/badge/agents/iamironz/ai-config-bundle/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.00063 | $0.01098 |
| Opus 5.5 | $0.00025 | $0.00439 |
| Sonnet 5.5 | $0.00013 | $0.00220 |
| Haiku 4.5 | $0.00006 | $0.00110 |
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.
This is a copy
89% identical to codebase-locator — 49 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 — 121 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.
KB / RAG Alignment
This subagent is intentionally read-disabled (grep/glob/list only). Do not provide policy guidance;
return only file locations and let the parent agent apply ai-kb/AGENTS.md + relevant rules.
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 :)
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 · 121 lines · 63 tokens per session scan A c7374dae8a6c
codebase-locator is an agent published in the GitHub repository iamironz/ai-config-bundle (2 stars, last pushed 7mo ago), licensed MIT. It adds 63 tokens to every session and 1,098 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to codebase-locator, differing in 49 lines, and is treated as a copy.
Other agents, from other repositories
nauro-planner
Use to plan a non-trivial change before any code is written. Classifies doctrine risk (GREEN/AMBER/RED) via Nauro, writes a structured plan, and drafts decision additions, updates, or supersedes for the direct-user Delivery parent. Returns a plan and never writes project truth or edits files.
nauro-reviewer
Use to review a PR or diff. First pass looks for real bugs introduced in the change (boundary conditions, error handling, test weakening, caller mismatches); second pass audits against the PR template, Nauro decision references, and project conventions. Read-only. Flags actionable code issues and blocks on hard-rule…
nauro-tech-lead
Use to set or maintain project direction. Reads Nauro decisions, session transcripts, and PR diffs; judges architectural choices against active doctrine; and drafts complete decision additions, updates, or supersedes for the direct-user Delivery parent. Never writes project truth.
nauro-investigator
Use to investigate Nauro use and development cycles across Claude and Codex logs. Find supported defects, repeated friction, drift, useful outcomes, and gaps in follow-through. Check current code and counterevidence. Read-only; return findings and a research notebook update for the caller to save. Invoke for a bounded…
nauro-executor
Use to implement an exact approved plan. Has full source edit and test access. Runs lint and tests before declaring done. Commits locally, drafts the PR, and never pushes or opens it. Never writes project truth.
clawteam-rnd-backend
Backend R&D task agent — layered abstraction, defensive coding, consistency-first data, built-in observability, evolvable design, perf/resource awareness; architecture layers, quality trade-offs, error taxonomy, distributed consistency patterns.