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 skills/s3yed/appie-kit/memory-searchnpx skills add S3YED/appie-kit --skill memory-searchgit clone --depth 1 https://github.com/S3YED/appie-kitWrote 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/skills/s3yed/appie-kit/memory-search)<a href="https://agentmods.dev/skills/s3yed/appie-kit/memory-search"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/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 | $0.00060 | $0.00787 |
| Opus 5 | $0.00030 | $0.00394 |
| Sonnet 5 | $0.00012 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00079 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Search
Search the Appie brain — daily logs, project notes, decisions, topics, and long-term memory.
When to Use
- User asks about past decisions, conversations, or context
- User says "remember when...", "what did we decide about...", "check my notes on..."
- You need project context, client info, or infrastructure details
- Looking up dates, events, or historical information
Memory Structure
All files are in ~/.hermes/memory/:
- Daily logs:
YYYY-MM-DD.md— raw daily notes - Topics:
topics/*.md— subject-specific knowledge - Projects:
projects/*.md— project documentation - Decisions:
decisions/*.md— recorded decisions - Infrastructure:
infrastructure/*.md— server/fleet notes - Plans:
plans/*.md— future plans - Research:
research/*.md— research notes
Top-level brain files in ~/.hermes/:
MEMORY.md— curated long-term memory (read this first)USER.md— info about the human (Seyed)TOOLS.md— tool configuration and fleet SSH detailsIDENTITY.md— agent identity
Search Commands
Full-text search across all memory files
grep -ril "SEARCH_TERM" ~/.hermes/memory/ ~/.hermes/MEMORY.md ~/.hermes/USER.md ~/.hermes/TOOLS.md 2>/dev/null
Search with context (shows surrounding lines)
grep -rin -C 3 "SEARCH_TERM" ~/.hermes/memory/ 2>/dev/null | head -60
List recent daily logs
ls -t ~/.hermes/memory/????-??-??.md 2>/dev/null | head -10
Read a specific daily log
cat ~/.hermes/memory/YYYY-MM-DD.md
Search by date range (e.g., March 2026)
ls ~/.hermes/memory/2026-03-*.md 2>/dev/null
Search topics
ls ~/.hermes/memory/topics/ 2>/dev/null
grep -ril "SEARCH_TERM" ~/.hermes/memory/topics/ 2>/dev/null
Search projects
ls ~/.hermes/memory/projects/ 2>/dev/null
grep -ril "SEARCH_TERM" ~/.hermes/memory/projects/ 2>/dev/null
Advanced: fuzzy search with script
python3 ~/.hermes/skills/productivity/memory-search/scripts/search.py "QUERY" [--limit 10] [--recent 7]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 95 lines · 60 tokens per session scan A 98d0f726a90e
memory-search is a skill published in the GitHub repository S3YED/appie-kit (7 stars, last pushed 9d ago), licensed MIT. It adds 60 tokens to every session and 787 once invoked, about $0.0003 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 skills, from other repositories
remember
Recall what was actually said or decided earlier — across daily summaries, the conversation buffer, files people sent, live sessions and scheduled runs. Use whenever someone refers to prior context ("what did we decide", "last time", "as I said", "the file I sent you", "what did you tell me"), or for any synonym of…
bot-state
Show where this bot's memory actually lives — state root, summaries, attachments, outbox, buffer, sessions — and what is in each. Use when asked where files go, why a summary or attachment is missing, or to check the bot's storage layout.
knowledge
Capture and structure institutional knowledge before it is lost. Activate for: institutional knowledge, knowledge capture, knowledge transfer, knowledge base article, knowledge management, preserve knowledge, what do they know, departing employee knowledge, exit knowledge, succession knowledge, tacit knowledge…
workplace-context
Activate for: workplace memory, person brief, team profile, organisation profile, add person, add project, add terminology, four-layer memory, communication style, stakeholder brief, post-meeting memory revision, who works on, team directory, revise workplace memory, organisation context. NOT for: basic memory CRUD…
setup
Activate for: configure agentic office, install agentic office, agentic office orientation, two-plugin architecture, create work.local, initialise workplace memory, agentic office getting started, configure agents, workplace configuration. NOT for: official productivity plugin setup (use /productivity:start).
context-loader
Activate for: load context, inject context, cross-domain context, context for this endeavour, relevant background, multi-domain context, what context do I need, before I work on this, context from HR, context from finance, context from ops, combine context, cross-domain brief, what should I know before starting. NOT…