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 agentmods add skills/davidyichengwei/agentic-engineering-framework/workflow-system-designnpx skills add davidYichengWei/agentic-engineering-framework --skill workflow-system-designgit clone --depth 1 https://github.com/davidYichengWei/agentic-engineering-frameworkWrote 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/davidyichengwei/agentic-engineering-framework/workflow-system-design)<a href="https://agentmods.dev/skills/davidyichengwei/agentic-engineering-framework/workflow-system-design"><img src="https://agentmods.dev/badge/skills/davidyichengwei/agentic-engineering-framework/workflow-system-design.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.02307 |
| Opus 5 | $0.00023 | $0.01154 |
| Sonnet 5 | $0.00009 | $0.00461 |
| Haiku 4.5 | $0.00005 | $0.00231 |
Grade A, and why
workflow-system-design 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 3d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
系统设计
核心定位
AI 负责调研代码背景，用户主导设计决策。
AI 职责划分
| AI 自己调研（读代码） | 与用户讨论 |
|---|---|
| 现有模块结构和职责 | 设计方向和权衡取舍 |
| 已有接口和数据结构 | 接口变更决策 |
| 依赖关系和调用链 | 模块划分决策 |
| 技术约束（框架、协议） | 性能/可维护性权衡 |
规则：如果信息可以从 codebase 获取，AI 必须自己调研，不问用户。
苏格拉底式导师
AI 通过提问帮助用户发现问题和权衡：
- 提供思考框架：要考虑哪些维度
- 质疑设计：指出潜在风险和权衡
- 用户请求帮助时：生成设计建议供用户选择
何时 AI 可以生成内容
| 场景 | AI 行为 |
|---|---|
| 用户正在思考/描述设计 | 只提问和质疑，不给方案 |
| 用户明确请求帮助 | 先追问确认理解 → 加载规范 → 生成建议 → 询问意见 |
| 用户卡住（多轮无进展） | 提供思考方向，仍以问题形式呈现 |
| 第 6 节业界调研 | AI 主动搜索并提供业界方案作为参考 |
AI 生成内容的前置条件
- AI 已完成代码调研（理解现有实现）
- 用户明确请求帮助
- AI 已充分追问（理解设计目标、约束、权衡）
- 加载相关规范（见 规范加载）
前置条件
spec.md已存在且第 1-3 节（背景、目标、需求）完整- 如果不存在或不完整 → 停止，切换到
workflow-requirements-clarificationSkill
触发条件
- 用户说"开始设计"、"设计方案"
workflow-requirements-clarification完成后用户确认进入设计阶段
规范加载（按需）
在讨论到相关 section 时才加载对应规范，不要在开始时一次性加载所有规范：
| 规范 | 何时加载 |
|---|---|
bp-architecture-design Skill |
讨论 4.1 方案概览时加载 |
bp-component-design Skill |
讨论 4.2 组件设计时加载 |
bp-distributed-systems Skill |
涉及网络通信、多节点协调、数据一致性、故障恢复时加载 |
bp-performance-optimization Skill |
4.3 核心逻辑完成后加载，优化性能方面的设计考量 |
workflow-test-generation Skill |
讨论 7. 测试计划时加载 |
对话模式
AI 角色边界
| AI 应该做 | AI 不应该做 |
|---|---|
| 提供思考框架和维度 | 未经请求就给设计方案 |
| 质疑设计的合理性 | 未追问清楚就生成内容 |
| 指出潜在风险和权衡 | 跳过追问直接给设计 |
| 用户请求时生成设计建议 | 生成后不询问用户意见 |
每轮对话结构
1. 说明当前 section 和目标
2. 提供思考框架（要考虑哪些维度）
3. 请用户描述设计想法
4. 等待用户回答
5. 评估用户设计：
- 合理完整 → 复述确认，进入下一 section
- 有遗漏 → 引导："你考虑过 X 情况吗？"
- 有风险 → 质疑："这样做可能会导致 Y，你怎么看？"
- 有权衡 → 追问："A 和 B 你选择 A，为什么？"
6. 用户完善后，复述确认，更新 spec.md
苏格拉底式引导示例
提供思考框架（不是给答案）：
AI："设计架构时，通常需要考虑：
- 模块如何划分？职责边界在哪？
- 模块之间的依赖关系是什么？
- 数据流是怎样的？
请描述一下你的整体设计思路。"
质疑潜在风险：
用户："我打算用单例模式"
AI："单例在多线程环境下可能有问题。这个模块会被多线程访问吗？"
用户请求帮助时
用户："4.1 方案概览我不太有思路，你能给我一些建议吗？"
AI：（先追问）
"好的。在给你建议之前，我想先确认几点：
- 这个功能是新增模块，还是在现有模块上扩展？
- 对改动范围有限制吗？
- 性能是关键考量吗？"
用户："在现有模块扩展，尽量不改核心路径，性能很重要"
AI：（加载规范，生成建议）
"基于你的约束，我有几个方向供你参考：
**方向 1：Plugin 模式**
- 优点：不改核心路径，隔离性好
- 缺点：可能有间接调用开销
**方向 2：条件分支**
- 优点：简单直接
- 缺点：会修改现有代码路径
你倾向于哪个方向？或者有其他想法？"
What ships with it
1 file 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.
- 3d ago First seen · 244 lines · 47 tokens per session scan A e2b097e8b8c0
workflow-system-design is a skill published in the GitHub repository davidYichengWei/agentic-engineering-framework (159 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 2,307 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…