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/scottrbk/forgetful/memory-searchgit clone --depth 1 https://github.com/ScottRBK/forgetfulWhat 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.00007 | $0.00337 |
| Opus 5 | $0.00003 | $0.00169 |
| Sonnet 5 | $0.00001 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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 3d 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
Memory Search
Search the Forgetful knowledge base for relevant memories.
Your Task
Perform a semantic search using execute_forgetful_tool("query_memory", {...}) with the user's query.
Query: $ARGUMENTS
Search Parameters
Use these parameters for the search:
{
"query": "<user's search query>",
"query_context": "User initiated search via /memory-search command",
"k": 5,
"include_links": true,
"max_links_per_primary": 3
}
If the query mentions a specific project, add project_ids filter.
Response Format
Present results clearly:
- Summary: Brief overview of what was found (or "No relevant memories found")
- Primary Memories: For each memory show:
- Title (with importance score)
- Key content snippet
- Tags
- Linked memories if relevant
- Suggestions: If results seem incomplete, suggest refining the query or creating a new memory
Example
User: /memory-search authentication patterns
You search and respond:
Found 3 memories about authentication patterns:
1. **FastAPI JWT Authentication** (Importance: 9)
JWT middleware using httponly cookies for security...
Tags: security, authentication, fastapi
2. **OAuth2 Decision** (Importance: 8)
Chose OAuth2 over API keys for user-facing auth...
Tags: decision, oauth, security
Related: Memory #45 (Session management approach)
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.
- 3d ago First seen · 60 lines · 7 tokens per session scan A 50af99ebb428
memory-search is a command published in the GitHub repository ScottRBK/forgetful (296 stars, last pushed 8d ago), licensed MIT. It adds 7 tokens to every session and 337 once invoked, about $0.0000 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
prd-triage
Triage pending findings on the active PRD.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
release
Prepare a release by updating docs and bumping the version.
everme-help
Print a concise EverMe plugin status + reference card.
issue-verify
Run all requiredchecks for the active issue and record the verified receipt.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.