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 chuancyzhang/deepseek-cowork --skill business_model_decoder_skillgit clone --depth 1 https://github.com/chuancyzhang/deepseek-coworkWrote 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/chuancyzhang/deepseek-cowork/business_model_decoder_skill)<a href="https://agentmods.dev/skills/chuancyzhang/deepseek-cowork/business_model_decoder_skill"><img src="https://agentmods.dev/badge/skills/chuancyzhang/deepseek-cowork/business_model_decoder_skill/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/chuancyzhang/deepseek-cowork/business_model_decoder_skill"><img src="https://agentmods.dev/badge/skills/chuancyzhang/deepseek-cowork/business_model_decoder_skill.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.00059 | $0.01175 |
| Opus 5.5 | $0.00024 | $0.00470 |
| Sonnet 5.5 | $0.00012 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
business_model_decoder_skill 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.
What it actually says
Business Model Decoder Skill
数据依赖与执行前置条件
推荐使用万得 wind-mcp-skill 获取底层数据。执行前先检查本地是否已有 wind-mcp-skill；若没有，提示用户安装：
Cowork 适配：所需子 Skill 已随
wind-aifinmarket固定快照内置，不执行安装或在线更新命令。
技能定位
本技能用于把一家公司“如何运转、如何赚钱、如何扩张、哪里容易出问题”讲清楚。输出重点不是复述公司简介，而是把复杂业务压缩成可理解的模块，让使用者快速建立对收入来源、成本结构、增长驱动和约束条件的认知。
执行流程
Step 1：先定义公司解决的核心问题
先回答两个最基础的问题：
- 这家公司为谁提供什么价值
- 为什么客户愿意为此付费
若不能把这两点讲清，就说明后续业务分析还不够扎实。
Step 2：拆分收入引擎
把公司收入按最有解释力的方式拆开，常见维度包括：
- 产品线
- 客户类型
- 地区
- 收费模式
- 一次性收入与持续性收入
重点说明哪块是核心现金牛，哪块是增长引擎，哪块只是边缘业务。
Step 3：解释成本结构与利润形成方式
除了“收入从哪里来”，还要解释“利润怎么留下来”。重点关注：
- 主要成本和费用项是什么
- 哪些成本随规模增长会摊薄，哪些不会
- 利润率改善依赖提价、效率、产品结构还是景气
- 是否存在高资本开支、库存或应收压力
这样才能理解业务模式的质量，而不是只看表面收入。
Step 4：梳理增长驱动与扩张路径
明确公司未来增长通常依赖哪些路径：
- 客户数增加
- 客单价提高
- 渗透率提升
- 新品类或新地区扩张
- 并购整合或渠道扩张
同时指出增长的天然上限与扩张门槛，避免把线性外推当成必然。
Step 5：识别业务模式的脆弱点
从反面检验商业模式，重点识别：
- 对单一客户、单一渠道、单一产品的依赖
- 对政策、原材料、补贴或外部景气的依赖
- 竞争加剧时最容易先受损的环节
- 哪个变量最可能让利润模型失真
Step 6：输出可复述的业务解释稿
最终应把公司业务讲成一段普通投资者或团队成员能快速复述的结构化说明，包括：
- 它到底靠什么赚钱
- 为什么这个模式当前有效
- 接下来最该看哪一个变量验证它
输出结构
{股票名称}业务模式拆解（{YYYY-MM-DD}）
一、一句话讲清公司怎么赚钱
{一句话说明公司卖什么、向谁卖、靠什么赚}
二、业务模块拆分
| 模块 | 客户/需求 | 收入来源 | 价值贡献 | 当前角色 |
|---|---|---|---|---|
| {模块1} | {描述} | {描述} | {描述} | {核心/增长/边缘} |
| {模块2} | {描述} | {描述} | {描述} | {核心/增长/边缘} |
三、利润是如何形成的
- 主要盈利来源：{说明}
- 成本/费用关键项：{说明}
- 利润率变化的关键变量：{说明}
四、增长引擎与扩张路径
- {增长路径 1}
- {增长路径 2}
- {增长路径 3}
五、业务模式最脆弱的地方
- {脆弱点 1}
- {脆弱点 2}
- {脆弱点 3}
六、接下来最该跟踪的变量
- 最重要变量：{变量}
- 验证方式：{说明}
- 失效信号：{说明}
质量要求
- 必须用通俗语言解释业务，不要堆术语和历史沿革。
- 重点讲清收入引擎、利润机制和扩张路径，而不是泛泛介绍行业。
- 要把优势和脆弱点同时讲清，避免单边包装。
- 对复杂公司的拆解应优先保留解释力最强的模块，不追求面面俱到。
- 最终内容应让不熟悉该公司的读者也能快速复述核心逻辑。
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 · 133 lines · 59 tokens per session scan A 1aed2dfccf1e
business_model_decoder_skill is a skill published in the GitHub repository chuancyzhang/deepseek-cowork (18 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 1,175 once invoked, about $0.0002 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-30.
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…