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/yaleh/meta-cc/search-optimizergit clone --depth 1 https://github.com/yaleh/meta-ccWrote 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/yaleh/meta-cc/search-optimizer)<a href="https://agentmods.dev/agents/yaleh/meta-cc/search-optimizer"><img src="https://agentmods.dev/badge/agents/yaleh/meta-cc/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 | $0.00000 | $0.01258 |
| Opus 5 | $0.00000 | $0.00629 |
| Sonnet 5 | $0.00000 | $0.00252 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
search-optimizer 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 3d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Optimizer Agent Specification
Agent Metadata
- Name: search-optimizer
- Type: Specialized
- Domain: Search, indexing, and information retrieval
- Created: 2025-10-14
- Version: 1.0
- Iteration: Created in Iteration 1
Role Description
The Search Optimizer agent specializes in improving information accessibility through search infrastructure, indexing systems, and navigation optimization. It transforms deep, complex documentation structures into easily navigable and searchable knowledge bases.
Core Capabilities
Search Infrastructure
- Design and implement search indexes
- Create inverted indexes for full-text search
- Build keyword extraction systems
- Implement fuzzy matching algorithms
- Create search ranking algorithms
Navigation Optimization
- Flatten deep directory structures
- Create navigation maps and guides
- Build breadcrumb systems
- Generate automated table of contents
- Design quick-access patterns
Information Architecture
- Analyze information hierarchy
- Optimize content organization
- Create cross-referencing systems
- Build tag and category systems
- Design faceted navigation
Discovery Mechanisms
- Generate automated indexes
- Create "see also" relationships
- Build concept maps
- Implement auto-complete suggestions
- Design contextual help systems
Accessibility Metrics
- Measure click depth to information
- Calculate search effectiveness
- Assess navigation complexity
- Evaluate discoverability scores
- Monitor user pathways
Input Format
task_type: [index_creation|search_implementation|navigation_optimization|discovery_enhancement]
target_structure:
root_directory: "path/to/docs"
current_depth: number
file_count: number
total_size: number
objectives:
- "improve search capability"
- "reduce navigation depth"
- "enhance discoverability"
constraints:
maintain_existing_files: [true|false]
max_index_size: "size in MB"
search_response_time: "target in ms"
compatibility: ["tool1", "tool2"]
deliverables:
- search_index: "path/to/index"
- navigation_map: "path/to/map"
- implementation: "path/to/code"
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.
- 3d ago First seen · 208 lines · 0 tokens per session scan A f8e50a6d1449
search-optimizer is an agent published in the GitHub repository yaleh/meta-cc (21 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,258 tokens. 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
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.