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 xushuodasd/VIBE-Claude-Plugin --skill vibe-ai-workflowgit clone --depth 1 https://github.com/xushuodasd/VIBE-Claude-PluginWrote 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/xushuodasd/vibe-claude-plugin/vibe-ai-workflow)<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-ai-workflow"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-ai-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/xushuodasd/vibe-claude-plugin/vibe-ai-workflow"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-ai-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.00019 | $0.02405 |
| Opus 5 | $0.00010 | $0.01203 |
| Sonnet 5 | $0.00004 | $0.00481 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
vibe-ai-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 11d 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.
AI工作流文档规范
1. 文档目的
规范AI工作流的编写标准,确保AI能按用户要求生成并执行工作流。
2. 工作流结构
一个简洁高效的AI工作流文档应包含:
- 基本信息:名称、目标
- 前置步骤:产物检查、依赖项确认
- 执行步骤:详细的执行流程和顺序
- 执行建议:专业建议和注意事项
- 成功标准:任务完成的判定条件
- 失败处理:异常情况的应对措施
- 输出成果:明确的交付物和保存位置
3. 执行要求
- 严格按照步骤执行
- 与用户保持深度沟通
- 记录关键信息和结果
- 遇到异常时按失败处理机制执行
- 确保输出成果符合用户预期
4. 文档管理
- 执行后根据实际情况更新文档
- 进行版本管理,确保使用最新版本
最佳实践:
人物体系工作流
工作流程
前置步骤:产物检查
-
检查创作规划文档:
- 确认
../小说基本信息文件夹/创作规划.md文件是否存在 - 如果不存在,提示用户先执行创作规划工作流
- 确认
-
检查世界观设定文件:
- 确认
../小说基本信息文件夹/世界观/目录下是否存在世界观设定文件 - 如果不存在,提示用户先执行世界观创作工作流
- 确认
-
读取相关文档:
- 读取创作规划文档,了解核心定位和目标读者
- 读取世界观设定文件,了解世界背景和规则
第一步:与用户沟通确定前期主要角色
-
角色范围界定:
- 与用户沟通:"作为网文作者,您希望在前期重点塑造哪些核心角色?通常包括主角、1-2个重要配角(如女主/男主、男二/女二)和1个主要反派"
- 明确前期主要角色清单,确保覆盖故事初期的核心人物
-
创作目标确认:
- 与用户沟通:"您希望这些角色具有什么样的特质和魅力?是热血逆袭、智计无双,还是情感细腻?"
- 了解用户的创作偏好和角色定位
-
优先级排序:
- 与用户共同确定角色创作的优先级
- 建议顺序:主角 → 重要配角 → 主要反派
- 确保每个角色都得到充分的创作时间和精力
第二步:与用户沟通创作主角
-
基础信息确认:
- 与用户沟通:"您希望主角的姓名、年龄、性别、身份和职业是什么?外貌形象有什么具体要求?"
- 记录用户的具体要求,作为创作基础
-
四维锚定沟通:
- 与用户沟通:"您希望主角的核心标签是什么?外在目标和内在动机分别是什么?"
- 与用户沟通:"主角面临的核心障碍是什么?您希望他/她有怎样的成长弧光?"
- 确保四维锚定符合用户的创作意图
-
立体性挖掘引导:
- 与用户沟通:"主角的性格特质、优点缺点是什么?有什么特殊癖好或口头禅?"
- 与用户沟通:"主角的能力特长、背景经历、情感世界如何设计?"
- 与用户沟通:"主角的生活细节和语言风格有什么特点?"
- 引导用户深入思考,提供专业建议
-
真实性确认:
- 与用户沟通:"您希望主角有哪些独特的记忆和经历?"
- 与用户沟通:"主角有什么矛盾和挣扎?如何让他/她更真实可信?"
- 确保人物真实立体,符合用户期望
-
文档化:
- 根据与用户的沟通结果,使用主角模板填写详细信息
- 将主角设定文档保存至
../人物信息/人物文档/目录 - 与用户确认文档内容,确保符合其创作意图
第三步:与用户沟通创作重要配角
-
基础信息确认:
- 与用户沟通:"您希望这个配角的姓名、年龄、性别、身份和职业是什么?外貌形象有什么具体要求?"
- 记录用户的具体要求,作为创作基础
-
独立设定沟通:
- 与用户沟通:"这个配角的核心欲望、核心立场是什么?"
- 与用户沟通:"您希望这个配角有怎样的独立故事线和成长弧光?"
- 确保配角有独立的人格和发展路径
-
立体性挖掘引导:
- 与用户沟通:"这个配角的性格特质、优点缺点是什么?有什么特殊癖好或口头禅?"
- 与用户沟通:"配角的能力特长、背景经历、情感世界如何设计?"
- 与用户沟通:"配角的生活细节和语言风格有什么特点?"
- 引导用户深入思考,提供专业建议
-
与主角关系确认:
- 与用户沟通:"这个配角与主角的相识契机是什么?"
- 与用户沟通:"他们之间有哪些关键互动?配角对主角有什么影响?"
- 与用户沟通:"他们的关系会如何动态变化?"
- 确保关系设计合理自然
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.
- 11d ago First seen · 174 lines · 19 tokens per session scan A f864a79a0383
vibe-ai-workflow is a skill published in the GitHub repository xushuodasd/VIBE-Claude-Plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 2,405 once invoked, about $0.0001 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-31.
Other skills, from other repositories
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR workflow, AI code review, and issue tracker bridge sync. Primary execution interface for multi-session feature work.
council-review
Perform a rigorous Carmack Council code review. Use when explicitly asked to review code, do a "council review", "carmack review", or invoke /council-review. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js)…
council-plan
Architect a feature with the Carmack Council before writing code. Use when explicitly asked to plan a feature, do a "council plan", "carmack plan", or invoke /council-plan. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo…
test-architect
Map testable surfaces, audit existing tests for quality, and write test specifications that prevent AI shortcuts. Use when asked to "audit tests", "specify tests", "test architect", "map test coverage", or invoke /test-architect. Two modes — audit (evaluate existing tests against Beck's principles) and specify (write…