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/richfrem/agent-plugins-skills/os-memorygit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWhat 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.00097 |
| Opus 5 | $0.00008 | $0.00048 |
| Sonnet 5 | $0.00003 | $0.00019 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
os-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 2d 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
/os-memory Command
Please run the os-memory-manager skill immediately.
You must read the automated daily logs in context/memory/, extract the permanent facts/decisions, check the L3 context/memory.md file for architectural conflicts, and carefully append the refined rules. After successful curation, move the processed logs to the archive folder.
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.
- 2d ago First seen · 9 lines · 16 tokens per session scan A e8a9085bde13
os-memory is a command published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 97 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
user-management
How to manage the user registry — creating users for new Slack/GitHub/GitLab/Linear identities, managing aliases, resolving users across platforms. Use when a new human interacts with the swarm or when user identity needs updating.
review-pr
Review a pull request (GitHub) or merge request (GitLab) and provide detailed feedback.
investigate-sentry-issue
Investigate and triage a Sentry error issue.
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
swarm-chat
Effective communication within the agent swarm using internal Slack.
close-issue
Close a GitHub or GitLab issue with a summary comment.