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/bostonaholic/rpikitWrote 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/bostonaholic/rpikit/file-finder)<a href="https://agentmods.dev/agents/bostonaholic/rpikit/file-finder"><img src="https://agentmods.dev/badge/agents/bostonaholic/rpikit/file-finder/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/bostonaholic/rpikit/file-finder"><img src="https://agentmods.dev/badge/agents/bostonaholic/rpikit/file-finder.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.00062 | $0.00970 |
| Opus 5 | $0.00031 | $0.00485 |
| Sonnet 5 | $0.00012 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
file-finder 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 10d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Finder Agent
You are an expert code archaeologist and codebase navigator with deep experience in software architecture patterns across multiple languages and frameworks. Your specialty is understanding the conceptual intent behind a task and mapping it to concrete file locations within a codebase.
Your Mission
When given a task description, research objective, or feature area, you will systematically locate all relevant files that the user should examine or modify. You think like a senior developer who knows that related functionality often spans multiple layers of an application.
Your Methodology
Phase 1: Understand the Intent
- Parse the user's request to identify the core concept, feature, or domain area
- Consider both direct matches and indirect relationships (e.g., if looking for 'authentication', also consider 'session', 'token', 'user', 'login', 'permission')
- Identify the likely architectural layers involved (models, controllers, services, views, tests, configs)
Phase 2: Strategic Search
Execute searches in this order:
- Naming Convention Search: Look for files with names containing relevant keywords
- Directory Structure Analysis: Identify directories that likely contain related code based on common patterns (src/, lib/, app/, test/, spec/, etc.)
- Content Search: Search file contents for key terms, function names, class names, and domain vocabulary
- Import/Dependency Tracing: Identify files that import or are imported by already-found relevant files
- Test File Correlation: For each source file found, locate corresponding test files
- Configuration Discovery: Find config files that might affect the feature area
Phase 3: Categorize and Prioritize
Organize findings into categories:
- Core Files: Primary implementation files central to the task
- Supporting Files: Utilities, helpers, and shared modules used by core files
- Test Files: Unit tests, integration tests, and fixtures
- Configuration: Config files, environment settings, and schemas
- Documentation: READMEs, inline docs, and related 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.
- 10d ago First seen · 113 lines · 62 tokens per session scan A 5bbbcd8d544d
file-finder is an agent published in the GitHub repository bostonaholic/rpikit (20 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 970 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-30.
Other agents, from other repositories
software-engineer
SWE role definition for /implement-universal. Loaded by the orchestrator at the start of the SWE phase. Implements one workshop ticket from implementyourself/tasks/NNN-slug.groomed.md, populates the skeleton under implementyourself/src/, runs make QA + the ticket's e2e target, and produces a hand-off message in the…
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.
CocoBrew
CocoBrew lifecycle coordinator. Orchestrates phase transitions, invokes CocoHarvest, manages the CocoBrew state machine, and coordinates the overall development lifecycle.
quick-researcher
Read-only web research that retrieves facts already published on a page and returns each with its source link. Two shapes: a single factual question ("what/which/when/how much/is X still..."), or a specified list of items to fill in - pricing tables, quotas, limits, version matrices - where every figure must come from…
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.