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/sliamh11/deus/resumenpx skills add sliamh11/Deus --skill resumegit clone --depth 1 https://github.com/sliamh11/DeusWrote 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/sliamh11/deus/resume)<a href="https://agentmods.dev/skills/sliamh11/deus/resume"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/resume.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.1 | $0.00030 | $0.00476 |
| Opus 5 | $0.00015 | $0.00238 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
resume 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
/resume — Load Context
Load persistent context from the vault.
The vault is mounted at /workspace/vault/. If it doesn't exist, check /workspace/extra/obsidian/Deus/ as a legacy fallback.
Steps
-
Resolve vault path and read permanent memory (full — it's compact):
VAULT_DIR="${DEUS_VAULT_DIR:-/workspace/vault}" [ ! -d "$VAULT_DIR" ] && VAULT_DIR="/workspace/extra/obsidian/Deus" cat "$VAULT_DIR/CLAUDE.md" -
Find recent session logs (default: last 3, or use number given as argument):
ls -t "$VAULT_DIR"/Session-Logs/*.md 2>/dev/null | head -${args:-3} -
For each session log: read frontmatter only (the YAML block between the two
---lines):awk '/^---/{n++} n==2{exit} {print}' <file>This gives ~10 lines per log (~80 tokens) instead of the full file (~900 tokens). Only read the full log if the user asks for details or context is unclear.
-
If a search term was given (e.g.
/resume auth), grep logs and read frontmatter of matches:grep -ril "<term>" "$VAULT_DIR/Session-Logs/" 2>/dev/null -
Summarize in 2–3 lines: ongoing context, pending tasks, ready to continue.
Argument Variants
/resume— CLAUDE.md + last 3 session frontmatters/resume 5— CLAUDE.md + last 5 session frontmatters/resume auth— + search logs for "auth", read frontmatters of matches/resume full— load last 3 session logs in full (use sparingly)
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 · 46 lines · 30 tokens per session scan A 2a50d636e1f4
resume is a skill published in the GitHub repository sliamh11/Deus (51 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 476 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
memcord
Privacy-first, self-hosted chat memory for OpenClaw — save and recall conversation history across sessions without any cloud dependency.
mem9
Persistent cloud memory for OpenClaw agents. Use when users say: "install mem9" "setup memory" "add memory plugin" "openclaw memory" "mem9 onboarding" "memory not working" "import memories" "upload sessions".
mem9
Persistent cloud memory for OpenClaw agents. Use when users say: "install mem9" "setup memory" "add memory plugin" "openclaw memory" "mem9 onboarding" "memory not working" "import memories" "upload sessions".
cortex
Personal knowledge compiler and memory system. Ingests raw sources (documents, notes, transcripts, captures) into a structured, interlinked knowledge base. Maintains living entity pages, learning analysis, and the MEMORY.md routing table. Replaces the librarian skill.
librarian
DEPRECATED — Use the cortex skill instead. Cortex v2 absorbs all librarian functionality (memory maintenance, knowledge organization, learning analysis) into a unified knowledge compiler. This skill is kept for backwards compatibility but all triggers now route to Cortex.
neuron-curated-memory
Use Neuron (the semantic-memory MCP server) the RIGHT way so its graph stays clean and useful. Before answering, load prior context; after answering, save a CURATED turn — 3-5 concept keywords (nouns/entities/tech, never verbs or filler), typed links with a short rationale, and never a self-link. This raises graph…