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/skynetcmd/m3-memory/writegit clone --depth 1 https://github.com/skynetcmd/m3-memoryWhat 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.00024 | $0.00121 |
| Opus 5 | $0.00012 | $0.00060 |
| Sonnet 5 | $0.00005 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
write 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
Call m3:memory_write with content="$ARGUMENTS", type="note", scope="user".
Report the resulting id and any contradiction events (memory_write returns supersede info if the new memory invalidates an older one).
If the user wanted a different type (decision, fact, preference, etc.), suggest /m3:save for the auto-classified path.
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 · 12 lines · 24 tokens per session scan A b30525fe8c08
write is a command published in the GitHub repository skynetcmd/m3-memory (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 24 tokens to every session and 121 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-30.
Other commands, from other repositories
translate
Translate the following documentation files to all supported languages.
spec-kitty-standalone
This host should read Spec Kitty's canonical standalone-invocation skill pack at.
ox-session-review
Command "ox-session-review" from sageox/ox, covering failure-mode watch-list (read first), from the ledger root. should print 0, phase 1 — scan & score (read-only), quality buckets (first match wins) and removal candidates.
review
You are an expert code reviewer. Your job is to review code changes and provide actionable feedback.
go
READY 작업을 현재 사용자의 명시적 요청으로 실행할 때 사용.
bmad-cis-design-thinking
Guide human-centered design processes using empathy-driven methodologies. Use when the user says "lets run design thinking" or "I want to apply design thinking".