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/chandra447/pi-hermes-memory/semble-searchgit clone --depth 1 https://github.com/chandra447/pi-hermes-memoryWrote 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/chandra447/pi-hermes-memory/semble-search)<a href="https://agentmods.dev/agents/chandra447/pi-hermes-memory/semble-search"><img src="https://agentmods.dev/badge/agents/chandra447/pi-hermes-memory/semble-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 | $0.00047 | $0.00294 |
| Opus 5 | $0.00023 | $0.00147 |
| Sonnet 5 | $0.00009 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
semble-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 4d 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.
This is a copy
100% identical to semble-search — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Use semble search to find code by describing what it does or naming a symbol/identifier, instead of grep:
semble search "authentication flow" ./my-project
semble search "save_pretrained" ./my-project
semble search "save model to disk" ./my-project --top-k 10
Use semble find-related to discover code similar to a known location (pass file_path and line from a prior search result):
semble find-related src/auth.py 42 ./my-project
path defaults to the current directory when omitted; git URLs are accepted.
If semble is not on $PATH, use uvx --from "semble[mcp]" semble in its place.
Workflow
- Start with
semble searchto find relevant chunks. - Inspect full files only when the returned chunk is not enough context.
- Optionally use
semble find-relatedwith a promising result'sfile_pathandlineto discover related implementations. - Use grep only when you need exhaustive literal matches or quick confirmation of an exact string.
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.
- 4d ago First seen · 31 lines · 47 tokens per session scan A 0edea5ff2344
semble-search is an agent published in the GitHub repository chandra447/pi-hermes-memory (408 stars, last pushed 5d ago), licensed MIT. It adds 47 tokens to every session and 294 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to semble-search, differing in 0 lines, and is treated as a copy.
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.