Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add DropFan/claude-code-plugins/plugin install chat-saverWrote 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/commands/dropfan/claude-code-plugins/search)<a href="https://agentmods.dev/commands/dropfan/claude-code-plugins/search"><img src="https://agentmods.dev/badge/commands/dropfan/claude-code-plugins/search/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/commands/dropfan/claude-code-plugins/search"><img src="https://agentmods.dev/badge/commands/dropfan/claude-code-plugins/search.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.00007 | $0.00830 |
| Opus 5.5 | $0.00003 | $0.00332 |
| Sonnet 5.5 | $0.00001 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Working directory: !
pwd - Current date: !
date '+%Y-%m-%d %H:%M' - Plugin root: ${CLAUDE_PLUGIN_ROOT}
Task
Search through saved conversation files for specific keywords, optionally filtered by date range.
User arguments: $ARGUMENTS
Step 0: Load Settings
Load settings from .claude/chat-saver.local.md following ${CLAUDE_PLUGIN_ROOT}/skills/conversation-export/references/settings-loading.md. Extract: save_dir.
Step 1: Parse Arguments
Parse arguments from $ARGUMENTS:
- keyword (required, unless
--tagis used) — The search term or phrase to find - --date YYYY-MM-DD — Search only in files from a specific date
- --from YYYY-MM-DD --to YYYY-MM-DD — Search within a date range
- --tag — Filter results to files containing the specified tag in their metadata (YAML frontmatter
tags:field, HTML<meta name="keywords">, or plain textTags:header line)
If no keyword and no --tag is provided, use AskUserQuestion to ask for a keyword.
When --tag is used without a keyword, list all files matching the tag (no content search needed — just check metadata). When used with a keyword, first filter by tag, then search within matching files.
Step 2: Find Target Files
- Use Glob to scan
<save_dir>for all conversation files (*.md,*.txt,*.html) - If no files exist, inform the user and exit
- Apply filters if specified:
- --date: Only include files whose filename starts with the exact date
- --from/--to: Include files whose filename date falls within the range (inclusive)
- Date comparison is based on the
YYYY-MM-DDprefix in filenames - --tag: Use Grep to search for the tag in file metadata. For
.mdfiles, search for the tag in the YAML frontmattertags:line. For.htmlfiles, search in the<meta name="keywords">tag. For.txtfiles, search in theTags:header line. Only keep files that contain the specified tag.
Step 3: Search Content
- Use Grep to search for the keyword in the filtered files:
- Use case-insensitive matching
- Include 2 lines of context before and after each match (
-C 2) - Use
output_mode: "content"to show matching lines
- Collect all matches grouped by file
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 · 79 lines · 7 tokens per session scan A 68b248cdb66f
search is a command published in the GitHub repository DropFan/claude-code-plugins (8 stars, last pushed 26d ago), licensed MIT. It adds 7 tokens to every session and 830 once invoked, about $0.0000 per session on Opus 5.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
url
Print the tlive web terminal/dashboard link + QR code.
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
full
Run the full hope pipeline — intent, shape, target, freeze as needed — then execute.
meeting-end
Stop the meeting Voice Memo, draft notes, and prepare follow-up email to attendees.
meeting-setup
Prepare for a meeting by syncing attendees to Contacts, creating prep reminders, and updating Calendar alerts.
meeting-start
Detect the current meeting, start a Voice Memo recording, and mark attendance.