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 commands/kyopark2014/agent-plugins/searchgit clone --depth 1 https://github.com/kyopark2014/agent-pluginsWhat 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.00008 | $0.01418 |
| Opus 5 | $0.00004 | $0.00709 |
| Sonnet 5 | $0.00002 | $0.00284 |
| Haiku 4.5 | $0.00001 | $0.00142 |
Grade A, and why
search 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- search — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Command
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Search across all connected MCP sources in a single query. Decompose the user's question, run parallel searches, and synthesize results.
Instructions
1. Check Available Sources
Before searching, determine which MCP sources are available. Attempt to identify connected tools from the available tool list. Common sources:
- ~~chat — chat platform tools
- ~~email — email tools
- ~~cloud storage — cloud storage tools
- ~~project tracker — project tracking tools
- ~~CRM — CRM tools
- ~~knowledge base — knowledge base tools
If no MCP sources are connected:
To search across your tools, you'll need to connect at least one source.
Check your MCP settings to add ~~chat, ~~email, ~~cloud storage, or other tools.
Supported sources: ~~chat, ~~email, ~~cloud storage, ~~project tracker, ~~CRM, ~~knowledge base,
and any other MCP-connected service.
2. Parse the User's Query
Analyze the search query to understand:
- Intent: What is the user looking for? (a decision, a document, a person, a status update, a conversation)
- Entities: People, projects, teams, tools mentioned
- Time constraints: Recency signals ("this week", "last month", specific dates)
- Source hints: References to specific tools ("in ~~chat", "that email", "the doc")
- Filters: Extract explicit filters from the query:
from:— Filter by sender/authorin:— Filter by channel, folder, or locationafter:— Only results after this datebefore:— Only results before this datetype:— Filter by content type (message, email, doc, thread, file)
3. Decompose into Sub-Queries
For each available source, create a targeted sub-query using that source's native search syntax:
~~chat:
- Use available search and read tools for your chat platform
- Translate filters:
from:maps to sender,in:maps to channel/room, dates map to time range filters - Use natural language queries for semantic search when appropriate
- Use keyword queries for exact matches
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.
- 2d ago First seen · 178 lines · 8 tokens per session scan A d6f518da7d0c
search is a command published in the GitHub repository kyopark2014/agent-plugins (4 stars, last pushed 25d ago), licensed MIT. It adds 8 tokens to every session and 1,418 once invoked, about $0.0000 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 commands, from other repositories
status
Show a comprehensive overview of the current Zilliz Cloud cluster — context, cluster details, databases, and collections with stats.
quickstart
Set up Zilliz Cloud CLI — install, authenticate, and configure your cluster context in one go.
improve-prompt
Analyze and enhance vague or incomplete prompts before execution.
commit
Create well-structured git commits with meaningful messages.
explain-code
Break down complex code into clear, understandable explanations.
refactor
Analyze code and suggest meaningful refactoring improvements.