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/dzmitrys-dev/supamem/sm-searchgit clone --depth 1 https://github.com/dzmitrys-dev/supamemWrote 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/dzmitrys-dev/supamem/sm-search)<a href="https://agentmods.dev/commands/dzmitrys-dev/supamem/sm-search"><img src="https://agentmods.dev/badge/commands/dzmitrys-dev/supamem/sm-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.00016 | $0.00208 |
| Opus 5 | $0.00008 | $0.00104 |
| Sonnet 5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
sm-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.
What it actually says
/sm-search
Search the project's dual-memory corpus for relevant chunks.
Usage
/sm-search <query>
Behind the scenes this calls supamem hook claude-code with a synthetic file path
to derive the query, then injects the top-k chunks into the conversation.
Examples
/sm-search billing webhook signature verification/sm-search how do we handle Yookassa retries/sm-search auth0 session middleware order
When to use
- You want semantic context without triggering an Edit (no file path needed)
- You want to verify what supamem will inject before making a change
- You're exploring the codebase's documented patterns
For automatic injection on Edit/Write, the PreToolUse hook installed by
supamem install --client claude-code already runs — no manual /sm-search
needed.
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 · 34 lines · 16 tokens per session scan A 8f769cf37368
sm-search is a command published in the GitHub repository dzmitrys-dev/supamem (12 stars, last pushed 14d ago), licensed MIT. It adds 16 tokens to every session and 208 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-30.
Other commands, from other repositories
AGENTS
The thirteen memory slash commands, registered once by the memory component through register.ts (registerMemoryCommands(pi, deps)). MEMORYCOMMANDNAMES: /memory /memfs /remember /init /doctor /recompile /memory-repository /sleeptime /reflect /dream /search /people /facts. Score 24 (53 files, DI surface, central…
save-session-learnings
Document session learnings to CLAUDE.md and AGENTS.md. Use after completing significant tasks, debugging sessions, or discovering project patterns.
kiro-steering-custom
Command "kiro-steering-custom" from gotalab/cc-sdd, covering kiro custom steering creation, workflow, available templates, steering principles and tool guidance.
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
wiki-synthesize
Synthesize wiki/sources/ .md pages from raw session transcripts using the configured LLM backend.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.