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/danielsimonjr/memory-mcp/searchgit clone --depth 1 https://github.com/danielsimonjr/memory-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/commands/danielsimonjr/memory-mcp/search)<a href="https://agentmods.dev/commands/danielsimonjr/memory-mcp/search"><img src="https://agentmods.dev/badge/commands/danielsimonjr/memory-mcp/search.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.00016 | $0.00662 |
| Opus 5 | $0.00008 | $0.00331 |
| Sonnet 5 | $0.00003 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
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 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.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Search
Search for files using Everything (instant indexed search) or fzf (fuzzy matching).
Default Behavior
By default, uses Everything for blazing-fast indexed file search across all drives.
Arguments
| Argument | Description |
|---|---|
<query> |
Search query (filename, pattern, or path) |
--fzf |
Use fzf fuzzy finder instead of Everything |
--content |
Search within file contents (fzf only) |
--info |
Get detailed file info (size, dates, attributes) |
Usage Examples
# Fast file search with Everything
/SEARCH claude.md
/SEARCH *.ts
/SEARCH ext:json memory
# Search with wildcards and filters
/SEARCH "src/*.test.ts"
/SEARCH "ext:exe;dll size:>1mb"
/SEARCH "parent:C:\mcp-servers *.md"
# Fuzzy search with fzf
/SEARCH config --fzf
/SEARCH readme --fzf
# Search file contents
/SEARCH "import.*memory" --content
/SEARCH "function search" --content
# Get detailed file info
/SEARCH package.json --info
Everything Search Syntax
Everything supports powerful search operators:
| Operator | Example | Description |
|---|---|---|
ext: |
ext:ts |
Filter by extension |
size: |
size:>1mb |
Filter by size |
dm: |
dm:today |
Date modified |
parent: |
parent:C:\src |
Search in directory |
* |
*.config.* |
Wildcard |
"..." |
"exact match" |
Exact phrase |
! |
*.ts !test |
Exclude |
| ` | ` | `*.ts |
When to Use Which
| Tool | Best For |
|---|---|
| Everything | Finding files by name, extension, path, size, date |
| fzf | Fuzzy/approximate matching, typo-tolerant search |
| fzf --content | Searching inside file contents |
Instructions
- Parse the query and flags from
$ARGUMENTS - If
--fzfflag is present, use fzf tools - If
--contentflag is present, usefuzzy_search_content - If
--infoflag is present, useget_file_info - Otherwise, use Everything
searchtool - Display results in a clean format
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 · 80 lines · 16 tokens per session scan A ec3703d0e437
SEARCH is a command published in the GitHub repository danielsimonjr/memory-mcp (3 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 662 once invoked, about $0.0001 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.