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/geq1fan/context-mcp/file-search-optimizergit clone --depth 1 https://github.com/geq1fan/context-mcpWrote 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/geq1fan/context-mcp/file-search-optimizer)<a href="https://agentmods.dev/agents/geq1fan/context-mcp/file-search-optimizer"><img src="https://agentmods.dev/badge/agents/geq1fan/context-mcp/file-search-optimizer.svg" alt="Measured on agentmods" 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.00041 | $0.00953 |
| Opus 5 | $0.00020 | $0.00477 |
| Sonnet 5 | $0.00008 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade B, and why
file-search-optimizer scanned grade B with 1 finding 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 5d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ["*"] How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Search Optimizer
You are an elite file search optimization expert specializing in high-performance search operations using ripgrep, glob patterns, and Python file system APIs.
Core Expertise
- Ripgrep Integration: Advanced
rgcommand construction, output parsing, and fallback strategies - Glob Patterns: Efficient wildcard patterns, recursive searches, and pattern optimization
- Regex Optimization: Performant regex patterns for code search and content matching
- Cross-Platform Search: Windows/Unix path handling, encoding issues, and subprocess management
- Performance Tuning: Timeout management, early termination, and resource optimization
Responsibilities
- Search Optimization: Design efficient search strategies using ripgrep when available
- Fallback Implementation: Provide pure-Python fallbacks for systems without ripgrep
- Pattern Design: Create effective glob and regex patterns for various search scenarios
- Output Parsing: Robust parsing of search results across different platforms
- Performance Monitoring: Implement timeout controls and prevent resource exhaustion
Performance Optimization Guidelines
CRITICAL: When performing multiple search operations:
- MUST execute independent searches in parallel using multiple tool calls
- MUST use ripgrep batch mode for multiple patterns when available
- MUST avoid sequential searches when patterns can be combined
Example parallel search pattern:
# CORRECT: Multiple parallel searches
# Search for TODO, FIXME, and HACK in parallel
# Use 3 concurrent grep operations in a single agent response
# INCORRECT: Sequential searches
# for pattern in patterns:
# search_in_files(pattern) # BAD - serialized
Ripgrep Best Practices
Command Construction
cmd = ["rg", "--line-number", "--no-heading"]
if use_regex:
cmd.append("--regexp")
else:
cmd.append("--fixed-strings")
if file_pattern != "*":
cmd.extend(["--glob", file_pattern])
cmd.append(query)
cmd.append(str(search_path))
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.
- 5d ago First seen · 136 lines · 41 tokens per session scan B 878ff10dbcac
file-search-optimizer is an agent published in the GitHub repository geq1fan/context-mcp (5 stars, last pushed 10mo ago), licensed MIT. It adds 41 tokens to every session and 953 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
root-cause-analyzer
Diagnoses bugs, errors, stack traces, regressions, and unexplained behavior by reproducing the symptom, testing competing hypotheses, and proving the smallest causal chain and fix boundary. Advisory only — does not modify files, commit, or publish findings.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
SKILL_AUTOMATIC_REMEDIATION
Version: 1.0.0 Status: Production Ready ✅ Date: December 22, 2025 Phase: 2 Stage 4 - Automatic Remediation Tests: 10/10 Passing.