Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/linshidream/skill-hubnpx agentmods add skills/linshidream/skill-hub/opc-sw-flowWrote 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/linshidream/skill-hub/opc-sw-flow)<a href="https://agentmods.dev/skills/linshidream/skill-hub/opc-sw-flow"><img src="https://agentmods.dev/badge/skills/linshidream/skill-hub/opc-sw-flow/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/linshidream/skill-hub/opc-sw-flow"><img src="https://agentmods.dev/badge/skills/linshidream/skill-hub/opc-sw-flow.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.00095 | $0.02781 |
| Opus 5.5 | $0.00038 | $0.01112 |
| Sonnet 5.5 | $0.00019 | $0.00556 |
| Haiku 4.5 | $0.00010 | $0.00278 |
Grade A, and why
opc-sw-flow 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPC Software Flow
目标
opc-sw-flow 是软件交付 OPC 的顶层编排协议。它不替代 product-lifecycle、dev-spec 或 dev-lifecycle，而是显式持有 engagement 工作区与一个或多个代码项目之间的映射，按阶段推进：
P1 product-lifecycle -> P2 dev-spec -> P3 dev-lifecycle -> released
核心判断：
- product 侧止于客户签字冻结的演示物和人话需求，不产出 spec。
dev-spec是 product 与 dev 的桥接 skill，但归属 dev 侧；scope 由代码项目根的.dev-flow.yml管。dev-lifecycle继续按既有协议消费.dev-flow-state.json，不由本 skill 改写。- product 工作区和 dev 代码项目默认解耦；跨文件夹交接靠
.opc-sw-flow-state.json显式映射和显式材料路径完成。
本 skill 是 protocol，不是控制器：它定义 phase、状态契约、转移规则和跨文件夹映射，具体执行由当前 agent 按可用工具完成。
opc-sw-flow 是 opc-<domain>-flow 家族的软件域成员。未来内容、咨询等业务域可以新增并列顶层编排，不需要改名或复用软开域协议。
使用场景
启动：
- "接了个活：{客户/项目名}"
- "启动 OPC 流程"
- "跑一遍软开全流程"
恢复：
- "继续 OPC 流程"
- "接着上次的活"
- 读取
.opc-sw-flow-state.json，从中断的 phase 继续
双重定位
opc模式：一人跑全链，phase 尽量连续推进。team模式：允许停在 product 签字、dev spec review 或代码 review 等人控交接点。
状态文件
在 engagement 工作区根维护 .opc-sw-flow-state.json，最小 schema 见仓库级 schemas/opc-sw-flow-state.schema.json。
关键字段：
| 字段 | 含义 |
|---|---|
current_phase |
顶层阶段，取值见下文 phase |
mode |
opc 或 team；决定 product 侧演示物档位 |
product_workspace |
product 工作区路径，通常就是 engagement 根 |
dev_projects |
代码项目 map，支持一个 engagement 对多个项目 |
handoff.requirements_doc_path |
product-lifecycle 输出的 需求签字记录.md 路径 |
handoff.prototype_path |
product-lifecycle 输出的演示原型目录路径 |
handoff.design_md |
product-lifecycle 输出的 DESIGN.md 路径（可选；P2 复制到各 dev 项目根）。注：上游 product-lifecycle state 字段名为 design_md_path，写入本字段时需做字段名转换（或用兼容别名 handoff.design_md_path，见下文） |
各 dev 代码项目仍在自身根目录维护 .dev-flow.yml、.dev-flow-state.json 和 docs/specs/。
dev_projects 写入时优先使用对象值：
{
"frontend-react": {
"root": "/repo/crm-web",
"kind": "frontend-react",
"status": "pending"
}
}
读取旧状态或临时状态时，也允许 "frontend-react": "/repo/crm-web" 这种简写；继续写回时应规范化为对象。handoff.requirements_doc 和 handoff.prototype_dir 是兼容别名；handoff.design_md_path 是 handoff.design_md 的兼容别名（对齐上游 product-lifecycle 的 design_md_path 字段名，避免映射时丢路径）；新状态使用 requirements_doc_path、prototype_path 和 design_md。
What ships with it
4 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.
- 1mo ago First seen · 174 lines · 95 tokens per session scan A 18acd66576b4
opc-sw-flow is a skill published in the GitHub repository linshidream/skill-hub (20 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 2,781 once invoked, about $0.0004 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-15.
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…