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 jl-cmd/claude-dream --skill dreamgit clone --depth 1 https://github.com/jl-cmd/claude-dreamWrote 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/jl-cmd/claude-dream/dream)<a href="https://agentmods.dev/skills/jl-cmd/claude-dream/dream"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dream/dream.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.00063 | $0.01033 |
| Opus 5 | $0.00032 | $0.00517 |
| Sonnet 5 | $0.00013 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
dream 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 8d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dream: Memory Consolidation
Overview
Consolidate auto memory by enforcing the format contract, pruning stale content, deduplicating facts, and rebuilding MEMORY.md as a clean index.
Announce at start: "Running memory consolidation (dream)."
Context: Standalone maintenance utility. Run periodically or when memory feels cluttered. Simulates the Auto Dream feature that is in gradual rollout.
The Format Contract
Source: Claude Code client system prompt + official docs.
MEMORY.md is an index, not a memory. It should contain only one-line pointers to topic files:
- Format:
- [Title](file.md) -- one-line hook - Target: under ~150 characters per entry
- Hard limit: 200 lines / 25KB (only this much loads at session start)
- No content, tables, or multi-line facts directly in MEMORY.md
Topic files require frontmatter:
---
name: {{topic name}}
description: {{one-line description}}
type: {{user | feedback | project | reference}}
---
Organization: Semantic by topic, not chronological by session.
The Process
Phase 1: Audit
Read MEMORY.md and every file in the memory directory. For each file, check:
- Frontmatter present? Must have name, description, type fields.
- Type correct? Must be one of: user, feedback, project, reference.
- Named by topic? Files named
session-YYYY-MM-DD-*should be renamed to their actual topic.
For MEMORY.md, check:
- Index entries only? Flag any line that is NOT a
- [Title](file.md)link or a##section header. - Content leaking into index? Flag inline facts, tables, multi-line bullet points.
- Under 200 lines? Flag if approaching the limit.
Phase 2: Propose Changes
Present a structured report to the user with these sections:
Format violations -- files missing frontmatter, content in MEMORY.md Stale content -- items older than 14 days with forward-looking TODOs or "Next/Pending" sections that may be completed Duplicates -- facts that appear in both topic files and MEMORY.md inline, or across multiple topic files Rename candidates -- session-dated files that should be topic-named Proposed actions -- numbered list of specific changes (extract, merge, prune, rename, add frontmatter)
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.
- 8d ago First seen · 119 lines · 63 tokens per session scan A e142b3b0bb4e
dream is a skill published in the GitHub repository jl-cmd/claude-dream (12 stars, last pushed 27d ago), licensed MIT. It adds 63 tokens to every session and 1,033 once invoked, about $0.0003 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 skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.