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.
git clone --depth 1 https://github.com/DevZonayed/MochiWrote 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/devzonayed/mochi/dream)<a href="https://agentmods.dev/commands/devzonayed/mochi/dream"><img src="https://agentmods.dev/badge/commands/devzonayed/mochi/dream/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/commands/devzonayed/mochi/dream"><img src="https://agentmods.dev/badge/commands/devzonayed/mochi/dream.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00897 |
| Opus 5.5 | $0.00010 | $0.00359 |
| Sonnet 5.5 | $0.00005 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00090 |
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 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are performing a rollup / dream on the continuum chain: collapsing the last N links into a single durable "phase digest" so the chain stays sub-linear in size while preserving decision lineage.
What to do
-
Gather the input package with the helper:
node "$(cat .continuum/.plugin-root)/lib/dream_prepare.js" --n ${ARGUMENTS:-25}Read the JSON output. Key fields:
rollupCandidateIds— ids that will be collapsedsummaries— id → summary text (this is your raw material)tagsUnion— superset of tags across candidates (use to choose digest tags)tsRange— first/last timestamp coveredcanProceed— if false, ABORT and tell the user why (fromwarnings)
-
Compose the digest summary in your head (~800 tokens). Rules:
- Merge duplicates. If link 0007 says "use MFA" and link 0009 says "use MFA via TOTP," collapse to one decision with the concrete value.
- Drop superseded-and-irrelevant. If link 0005 said "basic login" and link 0010 superseded with "MFA," the digest records ONLY MFA — but explicitly notes the supersession lineage ("MFA, supersedes earlier basic-login decision from this phase").
- Preserve decision lineage. Never silently drop a contradiction; state it as resolved.
- References, not payloads. If detail belongs in code/commits/archives, reference it — don't restate.
Use the structure:
## Phase digest: <ids> (<tsRange>) ## Resolved decisions - <decision> <lineage if superseding> ## Carried-forward open threads - <still-unresolved at end of phase> ## Constraints / Do not (cumulative) - <durable "do not" items> ## Dropped (no longer relevant) - <briefly: superseded items not worth carrying> ## Provenance - rolled-up links: <ids> -
Commit the rollup atomically with the finalize helper:
cat <<'CONTINUUM_DIGEST_EOF' | node "$(cat .continuum/.plugin-root)/lib/dream_finalize.js" --rollup-ids "<comma-separated-ids>" --tags "phase-digest,<other-tags-from-tagsUnion>" <YOUR DIGEST MARKDOWN HERE> CONTINUUM_DIGEST_EOFThe script prints the new digest link id. It:
- Writes the new digest link
- Moves all
rollup-idsdirectories fromchain/links/NNNN/tochain/links/_archived/NNNN/ - Appends a tombstone entry per archived link to
index.jsonl(originals are NEVER mutated) - Clears any pending-checkpoint sentinel
-
Do NOT regenerate
STATE.mdas part of dream. STATE.md is regenerated by/continuum:checkpoint, not rollup — rollup is purely a chain-compression operation that preserves history. -
Report back to the user: new digest id, range covered, count rolled up, and whether you noticed any contradiction worth surfacing.
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 · 75 lines · 25 tokens per session scan A 5a3702e3f746
dream is a command published in the GitHub repository DevZonayed/Mochi (3 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 897 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-08-31.
Other commands, from other repositories
context-stats
Display context window usage and token statistics.
handoff
Write a session handoff document for continuity.
hades-validate-memory
Validate every Asphodel memory file and report results.
pack
Pack target repo with repomix. Snapshot for AI context. Cached per featureid.
reflect
After the user triggers this command, run Learning Loop steps 4-8. Two phases: first half (review + organize) completes, then automatically continues to second half (re-analyze + trim + wrap up).
recover
Restore memory from your GitHub backup when local memory files are lost or corrupted. Also works for cross-device sync.