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/dgraziosi/foundation/dreamnpx skills add dgraziosi/foundation --skill dreamgit clone --depth 1 https://github.com/dgraziosi/foundationWrote 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/dgraziosi/foundation/dream)<a href="https://agentmods.dev/skills/dgraziosi/foundation/dream"><img src="https://agentmods.dev/badge/skills/dgraziosi/foundation/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 | $0.00043 | $0.01244 |
| Opus 5 | $0.00022 | $0.00622 |
| Sonnet 5 | $0.00009 | $0.00249 |
| Haiku 4.5 | $0.00004 | $0.00124 |
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 today.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dream
You are running Dream. Dream is the nightly vault pass. The user can run this, or attach it to Vault Keeper.
Dream rewrites the record from today's activity, closes what's done, and cleans obvious duplicates. One record at a time. Invent nothing.
Cite .agents/skills/foundation-mcp/ for which vault call to use. Cite .agents/skills/handoff/ when a step finishes. Look up the live vault schema at call time (bootstrap, inspect_ontology, or the server tool list). Do not trust a dump in this file.
The user is the human who runs this vault on this machine. The vault MCP is on this machine (http://127.0.0.1:8787). Stay on localhost. Do not tell anyone to expose it.
A record is the node (the system of record). Activity is the audit log. History stays in activity. Do not call the graph “the Vault.”
Vault Keeper still does not invent life facts. A bot running Dream may rewrite a record from that record's own activity.
Schedule and voice
02:00, all 7 nights, user-local. Overnight on purpose. Run Dream before backup when both exist. If a morning brief also exists, that clock is 08:00 user-local. Put these clocks on the bot's Routines. Do not add a live instance cron in git.
Quiet when the pass finished and nothing needs the user. Ping the user when you stopped because the activity does not say what is true, or when a destructive call needs a key with destructive scope.
This pass rewrites records that moved. Vault health, nightly backup, the weekly graph report (.agents/skills/graph-hygiene/), and product updates have their own schedules. That weekly report stays a report. Do not turn this pass into that report.
What Dream is not
- Not Letta sleep-time compute. Do not precompute the next query.
- Not Mem0 chat extract. Do not ingest mail or chat.
- Do not invent insight records.
- Do not write dues into standing harness memory. Dues stay on the record.
- Not a new vault call. Use
get,list_activity,upsert, andsearch. Destructive calls (delete,unlink,undo,manage_typeretire) need a key with destructive scope.delete,unlink, and node or edgeundoalso need if-match timestamps fromget. - Not a Viewer pass.
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.
- today Changed 759258356373
- 4d ago First seen · 59 lines · 43 tokens per session scan A 01c8b220c17e
dream is a skill published in the GitHub repository dgraziosi/foundation (1 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,244 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-08-31.
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…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…