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/proticom/gnosys/setup-dreamgit clone --depth 1 https://github.com/proticom/gnosysWrote 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/commands/proticom/gnosys/setup-dream)<a href="https://agentmods.dev/commands/proticom/gnosys/setup-dream"><img src="https://agentmods.dev/badge/commands/proticom/gnosys/setup-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.00000 | $0.00485 |
| Opus 5 | $0.00000 | $0.00243 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
setup-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 yesterday.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys setup dream
Configure Dream Mode for idle-time memory consolidation on this machine.
Usage
gnosys setup dream
Behavior
- Runs the interactive three-step Dream Mode setup flow.
- Enables or disables Dream Mode.
- Designates this machine as the dream node, or clears or keeps an existing designation.
- Chooses the dream provider and model and validates access when possible.
- Configures max runtime, minimum memories, night window, real system idle threshold, cooldown, minimum changed memories, hard LLM call cap, self-critique, summary generation, and relationship discovery.
- On macOS, installs or removes the single machine-level launchd agent (
com.gnosys.dream.plist) that runsgnosys dream run --scheduled.
Writes and side effects
- Updates the active Gnosys config
dreamblock in~/.gnosys/gnosys.json. - Writes or clears
dream_machine_idin the local central DB and mirrors it to the remote DB when configured and reachable. - Resets Dream Mode consecutive failure counters after setup completes.
- May read provider API keys from environment variables or platform secure storage.
Platform notes
macOS
- API keys: macOS Keychain (recommended), environment variables, or
~/.config/gnosys/.env - Machine designation: Stored in the local central DB; synced to remote when multi-machine sync is configured
- Shell profile:
~/.zshrcor~/.bash_profileif setting provider keys manually
Linux
- API keys: GNOME Keyring when
secret-toolis available, environment variables, or~/.config/gnosys/.env - Machine designation: Same as macOS — local DB with optional remote mirror
- Shell profile:
~/.bashrcor~/.zshrcfor manual env vars
Windows
- API keys: Environment variables or
~/.config/gnosys/.env - Machine designation: Same DB behavior; use PowerShell or System Environment Variables for keys
- Shell profile: PowerShell profile (
$PROFILE) for persistent env vars
Validation
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.
- yesterday First seen · 53 lines · 0 tokens per session scan A 9718a203197b
setup-dream is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 485 tokens. 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 commands, from other repositories
wrap
Close the session cleanly. Update entity state. Capture decisions. Detect momentum shifts.
start
"What accumulated? What's blocking? Where do I begin?".
promote
Move .memory/ artifacts to permanent knowledge locations.
checkpoint
Create or update .memory/ with current conversation state.
cleanup
Delete promoted content from the .memory/ directory.
gains
Show what Kage saved you — tokens, cost, stale memories blocked, stale knowledge caught.