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 skills add sliamh11/Deus --skill learn-thisgit 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/learn-this)<a href="https://agentmods.dev/skills/sliamh11/deus/learn-this"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/learn-this/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sliamh11/deus/learn-this"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/learn-this.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.01541 |
| Opus 5.5 | $0.00012 | $0.00616 |
| Sonnet 5.5 | $0.00006 | $0.00308 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
learn-this 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 1mo 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/learn-this
Teach the user something and make the learning stick across sessions by persisting it into the semantic memory vault, so the next session (and any project) can recall what they already know.
This is the vault-native sibling of /teach. Where /teach builds a directory-based,
multi-week course workspace (mission file, lesson HTML, local learning-records), /learn-this
keeps no local workspace: it writes each learning as a vault memory node retrievable anywhere
via memory_tree.py, and grounds knowledge in NotebookLM rather than parametric guessing.
Relationship to /teach (read this — single source of truth)
/teach→ a self-contained course workspace in the current directory. Best for a sustained, structured curriculum with rich interactive HTML lessons./learn-this→ lightweight, cross-session learning capture into the global vault + NotebookLM. Best for "teach me X and remember that I learned it" across projects.
Never duplicate a learning record across both. A /teach workspace owns its local
learning-records/; /learn-this owns $VAULT/Learning/. If a learning relates to a /teach
course, link it with a see_also edge — do not copy it.
Steps
1. Resolve the vault path
Read ~/.config/deus/config.json and use its vault_path. If DEUS_VAULT_PATH is set, use that
instead. All paths below use $VAULT for this resolved path. (Same resolution as /checkpoint,
/compress, /preserve — keep it portable; never hardcode a personal path.)
2. Establish the mission
Understand why the user wants to learn this — the concrete real-world goal it serves. This grounds every teaching choice. If it is unclear, ask before teaching; a vague mission produces abstract, ungrounded lessons. The mission is captured inside the first learning node (step 6), not in a separate file.
3. Compute the zone of proximal development — from the vault
Query the vault for what the user already knows on this topic:
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.
- 1mo ago First seen · 129 lines · 31 tokens per session scan A 768d5d08c447
learn-this is a skill published in the GitHub repository sliamh11/Deus (52 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,541 once invoked, about $0.0001 per session on Opus 5.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.
Research for Datacore
Automated research — source processing, podcast generation, and knowledge extraction.
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".
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…
neuron-usage
Correct-usage playbook for the Neuron semantic memory MCP (neuron tools). Use when storing or recalling memories with Neuron, when deciding what to pass to preturn/storeturn, when the user says "remember this", "salva in memoria", "cosa ricordi di", "usa neuron", when curating keywords/links for the knowledge graph…