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 skills add glide-the/im-dream --skill dream-story-workflowgit clone --depth 1 https://github.com/glide-the/im-dreamWrote 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/glide-the/im-dream/dream-story-workflow)<a href="https://agentmods.dev/skills/glide-the/im-dream/dream-story-workflow"><img src="https://agentmods.dev/badge/skills/glide-the/im-dream/dream-story-workflow/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/glide-the/im-dream/dream-story-workflow"><img src="https://agentmods.dev/badge/skills/glide-the/im-dream/dream-story-workflow.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.00026 | $0.00448 |
| Opus 5.5 | $0.00010 | $0.00179 |
| Sonnet 5.5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
dream-story-workflow 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 12d 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.
What it actually says
Dream Story Workflow
Use this workflow when the user asks to create or revise a story, outline, character set, scene plan, or storyboard in Dream.
唯一产品生命周期是：
Agent 构建 canonical 产物 -> 宿主自动同步产物并渲染页面 -> 一次确认 -> 同一 Chat Agent 构建首集产物工作台
Before creating Dream assets, read references/dream-file-sync.md completely
and follow its canonical-file and controlled-tool sequence.
Rules
- Preserve the locked Deck voice and constraints supplied in
<deck_context>. - Write durable story assets in the current Chat workspace; do not return a standalone proposal JSON as a substitute for workspace files.
- canonical 文件完整可读后直接结束 turn；宿主 Hook 负责稳定同步页面和
.dream，MCP 写工具只做即时预览或显式修复。 - Dream confirmation 是创作者的一次确认且正文对用户可见：应用修改后在同一 thread 写入 EP01 的
episode-outline.md、script.md、storyboard.yaml、review-report.md，不能只回复正文。 - 收到 Dream confirmation 后第一动作必须是内建 Write/Edit；不先规划、解释或研究 schema，不调用 Dream MCP 更新 stage。即使上一次失败已留下文件，也必须覆盖四项 Episode 文件；
storyboard.yaml的shot_id必须是带引号的 ASCII 字符串（如"shot-001"），数字shot_id: 1无效。四项文件写完即结束，stage、.dream发布和 Episode 关联由宿主成功 Hook 处理。 - Never invent a WorkflowRun, actor, thread, source provenance, revision, or path.
- Do not introduce item-by-item approval, rejection, retry, archive, or another confirmation step.
For ordinary questions that do not create or revise Dream assets, answer normally.
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.
- 12d ago First seen · 33 lines · 26 tokens per session scan A a30b53748344
dream-story-workflow is a skill published in the GitHub repository glide-the/im-dream (0 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 448 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-10-02.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…