Clowder AI is a self-hosted workspace where AI agents from different model families work together as a persistent team, retaining identities, shared evidence, and memory across tasks. It is for people who want to coordinate multiple AI agents without repeatedly rebuilding their context.
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 zts212653/clowder-ai --skill co-creation-storytellinggit clone --depth 1 https://github.com/zts212653/clowder-aiWrote 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/zts212653/clowder-ai/co-creation-storytelling)<a href="https://agentmods.dev/skills/zts212653/clowder-ai/co-creation-storytelling"><img src="https://agentmods.dev/badge/skills/zts212653/clowder-ai/co-creation-storytelling/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/zts212653/clowder-ai/co-creation-storytelling"><img src="https://agentmods.dev/badge/skills/zts212653/clowder-ai/co-creation-storytelling.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.00162 | $0.02343 |
| Opus 5.5 | $0.00065 | $0.00937 |
| Sonnet 5.5 | $0.00032 | $0.00469 |
| Haiku 4.5 | $0.00016 | $0.00234 |
Grade A, and why
co-creation-storytelling 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 6d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Co-creation Storytelling — 长故事中的人、猫与变化
把共同经历压缩成观众能复述的故事,同时保住人物、证据和变化。源自一次真实返工:时间被混淆,临时远程演示被戏剧化;组织成立盖住猫的成长,评估与执行方法被缩成书架,托付与进化被缩成口号。具体反例见 失败模式。
何时用,在哪里停
- 用于真实成长故事、团队共创经历、长期项目故事的取材与叙事。人机协作是重要分支,不是每个故事都要加猫。
- 排版/图已定只改颜色或错字,直接交制作技能;虚构故事不套事实取证;技术可信度分析交 tech-writing;讨论成长不启动 capability-evolution。
- 如果问题转为“别人的产品怎样带用户看懂、选择、亲手参与”,路由到 concept-demo-design 的参考拆解入口;共用的交互叙事方法只在该分支读取,不给历史故事追加登录、授权或引导编排清单。
- 先消费已有受众、材料、事实订正与授权,继续可做的工作。只问缺失且会改变叙事的事实或价值取舍,不让人重新写 brief。
- 本技能不自动发送他人、发布或生成媒体。已授权制作时,把叙事稿接给相应技能继续完成,不重复要求确认。
1. 确定这次讲给谁、要让人理解什么
先按叙事清晰度确定陌生读者要理解的一件事,再处理下面的历史与贡献。纯机制说明可用示意任务,由漫画/PPT/图像制作技能承接,不强套成长史。
写一句目标:观众看完能理解「谁遇到什么问题,做了什么,事情怎样改变」。 确定页数/时长、可公开边界和语气。借来的模板、四格漫画、时间轴只是候选容器,不先锁死格数。
需要时区分两个问题:
- 故事中的共创:当年人、猫及其他伙伴各做了什么,彼此怎样变化?
- 这次作品的共创:谁提供事实、校准意义、查证、组织、校稿和制作? 前者决定主线;后者用于署名或复盘。不要把制作过程混进历史,除非明确作为“今天我们还在一起创造”的回扣。
2. 把散落材料还原成可信的经历
沿当前故事范围找原始聊天、已经订正的口径、作品与版本记录;搜到摘要再读原文。家内长故事可从 memory-navigation 选择检索入口,已有精确路径直接读。
事实记录至少能回答:发生时间 / 谁做了什么 / 来源 / 当时状态 / 可公开程度。优先复用现有 story bible,别为每个风格另造事实账本。
- 个人经历以当事人明确订正为准;技术完成情况读对应版本与验收证据。两类来源分别管自己的 claim。
- 叙事复盘可借语气,戏剧化细节不能升级为事实。冲突写清哪条被订正、哪条尚未知。
- 入职与获奖、创建与完成、后来具备的能力与早期能力分开;没有猫的时期不提前放猫。
- 未核实的比例、精确时刻、学校/客户/同事标识,按需要核实、模糊或省略;不因画面好看补造。
- 已发生 / 正在推进 / 方向示意分别表达;生成画面能解释机制,不能证明机制已完成。
- 证据分级与验收缺口留在底稿。面向观众,用「正在探索」等自然时态交代必要边界,不让审计式免责声明盖过人物与行动。
3. 按变化取材,保留各方的行动
对可能进入主线的节点,写清下面这条链;取材表可按需使用,不要求每段填满:
当时卡在哪 → 谁采取了什么行动 → 共同产物或做法怎样改变 → 因而能继续做什么
先拆人和猫的动作,再写“我们”。按材料分配主动性,不固定成“人只定目标、AI 只执行”: 人可能试验、编码、研究、学习判断;猫可能提出方案、查证、反驳、实现、复核。组织与其他人的贡献也按证据保留,不编贡献比例。
特别找两种容易漏的成长:
- 人的变化:从亲自搬运、逐项盯办,逐渐能判断方案、证据与重要取舍;有具体经历才写。
- 猫和共同环境的变化:看得见彼此、能延续经历、能检查与改进做法。既讲“留下了什么”,也讲“怎么形成、后来怎么用”。
时间相邻不自动构成因果。没有证据连接两事,可并列为同类探索,不编成命定伏笔。多年日常积累不画成空白;也不为每年硬凑一次高潮。
4. 给看不见的工作一个可看见的动作
每个关键能力用「行动者 + 动词 + 对象 + 可见变化」写一句话,再选场景。
- “传话很累” → 人把讨论发给另一工具,再搬方案去写代码、搬代码去检查。
- “会评估” → 一起确定什么算好,选例子,再比较改动的效果。
- “有轨迹” → 回看输入、工具动作与结果,找到问题发生在哪一步。
- “真正托付” → 人交代;猫跨时间准备、跟进;需要判断时带着材料回来。
- “会进化” → 猫围绕目标研究、准备评估、尝试比较;重要采用决定由有权的人作出。
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago Changed e5a27d672199
- 1mo ago First seen · 108 lines · 162 tokens per session scan A d6ea88d39b39
co-creation-storytelling is a skill published in the GitHub repository zts212653/clowder-ai (3,471 stars, last pushed today), licensed MIT. It adds 162 tokens to every session and 2,343 once invoked, about $0.0006 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-09-17.
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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…