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/dream-rungit 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/dream-run)<a href="https://agentmods.dev/commands/proticom/gnosys/dream-run"><img src="https://agentmods.dev/badge/commands/proticom/gnosys/dream-run.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.00697 |
| Opus 5 | $0.00000 | $0.00349 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
dream-run 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 4d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys dream run
Force a Dream Mode consolidation cycle now. Same behavior and options as bare gnosys dream.
Usage
gnosys dream run
gnosys dream run --max-runtime 30
gnosys dream run --json
gnosys dream run --force
gnosys dream run --no-critique --no-summaries
Options
| Option | Description |
|---|---|
--max-runtime <minutes> |
Max runtime in minutes (default: 30) |
--no-critique |
Skip self-critique phase |
--no-summaries |
Skip summary generation |
--no-relationships |
Skip relationship discovery |
--force |
Run even if this machine is not the designated dream node |
--scheduled |
Apply designated-machine, night-window, real-idle, and dreamworthiness gates (used by launchd) |
--json |
Output raw JSON report instead of formatted text |
When --scheduled is set, the run acquires ~/.gnosys/dream.lock, exits cheaply unless all gates pass, and honors dream.maxLLMCallsPerRun. Every run (including skips) is appended to ~/.gnosys/dream-runs.jsonl.
Behavior
- Resolves configured stores via
GnosysResolver. - Loads config from the primary store path.
- Verifies
gnosys.dbis migrated (v2.0). - Checks designated-machine policy against the central DB.
- Runs
GnosysDreamEngine.dream()with phase progress on stderr. - Prints
formatDreamReport(report)to stdout, or JSON when--jsonis set.
Progress lines appear on stderr:
Starting Dream Mode cycle...
[phase-name] detail...
Prerequisites
- At least one Gnosys store (run
gnosys initfirst). - Migrated
gnosys.db(rungnosys migrateif needed). - Dream Mode provider/model configured (see
gnosys setup dream).
Designated machine
When the central DB records a designated dream machine, manual runs on other machines are blocked unless --force is passed:
Dream is designated to machine <id>, but this is <local-id>.
Pass --force to run anyway, or run 'gnosys setup dream' to redesignate.
Errors
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.
- 4d ago First seen · 89 lines · 0 tokens per session scan A 5a8d19ea89bd
dream-run is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 697 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-08-31.
Other commands, from other repositories
test-e2e
Write end-to-end tests for critical user journeys.
export
Design public API exports.
newpkg
Generate new package with Nx.
cb-search
코드브레인 BM25 검색 — stale 자동 refresh.
decide
Capture a strategic decision so it never gets lost or reopened accidentally.
perf-investigate
Drive an iOS performance or memory-leak investigation on using Memory Graph + Time Profiler. Enforce data-before-architecture and stacked PRs.