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/pedromosquera/squadai/memory-searchgit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/memory-search)<a href="https://agentmods.dev/commands/pedromosquera/squadai/memory-search"><img src="https://agentmods.dev/badge/commands/pedromosquera/squadai/memory-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.00012 | $0.00264 |
| Opus 5 | $0.00006 | $0.00132 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
memory-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.
What it actually says
Search project memory for entries matching the query.
The query is: $ARGUMENTS
If no query was provided, ask the user: "What are you looking for in project memory?"
Run:
squadai memory search "$ARGUMENTS" --json
Parse the JSON results and format them as a numbered list:
1. [0.82] docs/memory/auth/jwt-decision.md: We chose HS256 because the service is stateless…
2. [0.74] docs/memory/infra/db-migration.md: Migrations run at startup via golang-migrate…
3. [0.61] docs/memory/_inbox/payment-retry.md: Draft — exponential backoff for payment retries…
Each line: <rank>. [<score>] <path>: <first non-empty line of the note body>
If results are found, offer: "Would you like me to read any of these in full?" Read only the files the user requests (one or two at most).
If no results are returned, say:
No entries found in docs/memory/ matching "<query>". Consider running /memory-add to capture something new.
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 · 32 lines · 12 tokens per session scan A 2f0988a89f58
memory-search is a command published in the GitHub repository PedroMosquera/squadai (8 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 264 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
context-save
An elite context engineering specialist focused on comprehensive, semantic, and dynamically adaptable context preservation across AI workflows. This tool orchestrates advanced context capture, serialization, and retrieval strategies to maintain institutional knowledge and enable seamless multi-session collaboration.
save-session-learnings
Document session learnings to CLAUDE.md and AGENTS.md. Use after completing significant tasks, debugging sessions, or discovering project patterns.
init-workspace-flow-discovery
Phase 3 Discovery of init-workspace-flow.
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
init-workspace-flow-questions
Phase 8 Questions of init-workspace-flow.
kiro-steering-custom
Command "kiro-steering-custom" from gotalab/cc-sdd, covering kiro custom steering creation, workflow, available templates, steering principles and tool guidance.