Borrowing it
Nothing to install: this file belongs to walm00/business-context-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/walm00/business-context-os/main/.claude/skills/daydream/SKILL.mdgit clone --depth 1 https://github.com/walm00/business-context-osWrote 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/walm00/business-context-os/daydream)<a href="https://agentmods.dev/skills/walm00/business-context-os/daydream"><img src="https://agentmods.dev/badge/skills/walm00/business-context-os/daydream/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/skills/walm00/business-context-os/daydream"><img src="https://agentmods.dev/badge/skills/walm00/business-context-os/daydream.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.00031 | $0.02276 |
| Opus 5 | $0.00015 | $0.01138 |
| Sonnet 5 | $0.00006 | $0.00455 |
| Haiku 4.5 | $0.00003 | $0.00228 |
Grade B, and why
daydream scanned grade B with 1 finding 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 11d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/quality/last-daydream.txt 2>/dev/null || echo "no previous run" How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daydream
Purpose
This skill IS:
- A structured way to step back and reflect on your context architecture
- A tool for identifying what's missing, what's changed, and what's next
- A creative space for "what if" thinking about your business context
- A bridge between daily maintenance and strategic evolution
This skill IS NOT:
- An audit (use context-audit for that)
- A planning tool (use clear-planner for that)
- Something you need to do every day (weekly or when inspiration strikes)
When to Use
- End of week: "What did we learn this week that should change our context?"
- Before strategy sessions: "Is our context architecture ready for the conversation?"
- After market shifts: "Has our world changed enough to rethink our architecture?"
- When feeling stuck: "What are we not seeing?"
- When a new team member joins: "Does our context make sense to a fresh pair of eyes?"
The Daydream Process
Phase 1: What Changed Since Last Time (5 min)
Step 1: Find when daydream last ran
Check .claude/quality/last-daydream.txt for the timestamp. If the file doesn't exist, this is the first run — use 2 weeks ago as the baseline.
# Read last run timestamp (or default to 2 weeks ago)
cat .claude/quality/last-daydream.txt 2>/dev/null || echo "no previous run"
Step 2: Check git for USER DOCUMENT changes only
Scope to docs/ only — exclude .claude/, sessions, agents, skills, and framework files:
# Only user documents — NOT agents, skills, sessions, or framework docs
git log --since="{last_daydream_date}" --name-only --pretty=format:"%h %s (%ar)" -- docs/ ':!docs/_bcos-framework/methodology/' ':!docs/_bcos-framework/guides/' ':!docs/_bcos-framework/templates/'
This shows ONLY changes to user-created content: data points, table-of-context.md, current-state.md, document-index.md, and any other user docs. Ignores all BCOS framework files and .claude/ internals.
If nothing changed → short daydream. Report "No document changes since last run" and skip to Phase 3 (Imagine) for forward-looking reflection only.
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.
- 11d ago First seen · 232 lines · 31 tokens per session scan B b8cfa05e3162
daydream is a skill published in the GitHub repository walm00/business-context-os (21 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 2,276 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…
wiki-cli
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.