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/rangerrick337/operator-os/memorygit clone --depth 1 https://github.com/rangerrick337/operator-osWrote 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/rangerrick337/operator-os/memory)<a href="https://agentmods.dev/commands/rangerrick337/operator-os/memory"><img src="https://agentmods.dev/badge/commands/rangerrick337/operator-os/memory.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.00000 | $0.00019 |
| Opus 5 | $0.00000 | $0.00010 |
| Sonnet 5 | $0.00000 | $0.00004 |
| Haiku 4.5 | $0.00000 | $0.00002 |
Grade A, and why
memory 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 today.
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
Read and follow Operator Team OS/4. Workflows/memory.md.
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.
- today First seen · 4 lines · 0 tokens per session scan A 39a619dfc34a
memory is a command published in the GitHub repository rangerrick337/operator-os (10 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 19 tokens. 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-09-04.
Other commands, from other repositories
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.
memory-review
Display current memory state with timestamps, sizes, and staleness indicators.