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-architecturegit 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-architecture)<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-architecture"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-architecture/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-architecture"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-architecture.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.00026 | $0.01739 |
| Opus 5 | $0.00013 | $0.00870 |
| Sonnet 5 | $0.00005 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
vibe-architecture 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.
This is a copy
83% identical to smart-search — 243 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
架构设计文档工作流
1. 文档目的
规范架构设计文档的编写标准，确保AI能按照项目实际情况，生成包含技术栈、模块划分、数据流、部署架构的完整架构设计文档。
2. 工作流结构
一个简洁高效的架构设计文档工作流应包含：
- 基本信息：名称、目标
- 前置步骤：产物检查、依赖项确认
- 执行步骤：详细的执行流程和顺序
- 执行建议：专业建议和注意事项
- 成功标准：任务完成的判定条件
- 失败处理：异常情况的应对措施
- 输出成果：明确的交付物和保存位置
3. 执行要求
- 严格按照步骤执行
- 与用户保持深度沟通
- 记录关键信息和结果
- 遇到异常时按失败处理机制执行
- 确保输出成果符合用户预期
4. 工作流程
前置步骤：产物检查
-
检查项目根目录README.md：
- 确认项目根目录是否存在README.md文件
- 读取README.md文件，了解项目基本信息和主要功能
-
检查项目目录结构：
- 查看项目的完整目录结构
- 确认是否存在配置文件、依赖文件等
-
检查项目文档：
- 查看
doc/目录下的工作流程文档 - 了解项目的开发规范和工作流程
- 查看
第一步：了解项目需求
-
分析项目README：
- 理解项目的定位、目标和主要功能
- 识别项目的核心业务逻辑
-
分析项目目录结构：
- 分析
.vibe/目录下的开发规则 - 分析
doc/目录下的工作流程文档 - 理解项目的组织方式和设计思路
- 分析
-
识别项目技术栈：
- 检查项目中是否存在package.json、requirements.txt等依赖文件
- 分析项目中使用的编程语言、框架和库
第二步：设计技术栈方案
-
前端技术栈：
- 分析项目中是否存在前端代码
- 确定前端使用的框架、库和工具
- 记录前端技术栈的版本和配置
-
后端技术栈：
- 分析项目中是否存在后端代码
- 确定后端使用的语言、框架和数据库
- 记录后端技术栈的版本和配置
-
AI相关技术：
- 分析项目中是否使用了AI相关技术
- 确定AI模型、算法和工具
- 记录AI技术的版本和配置
第三步：设计模块划分
-
前端模块：
- 基于项目功能，划分前端模块
- 确定每个模块的职责和功能
- 设计模块间的交互方式
-
后端模块：
- 基于项目功能，划分后端模块
- 确定每个模块的职责和功能
- 设计模块间的交互方式
-
AI模块：
- 基于项目功能，划分AI模块
- 确定每个模块的职责和功能
- 设计模块间的交互方式
第四步：设计数据流
-
前端数据流：
- 设计前端页面间的数据传递
- 设计前端与后端的数据交互
- 设计前端状态管理方案
-
后端数据流：
- 设计后端模块间的数据传递
- 设计后端与数据库的数据交互
- 设计后端与AI模块的数据交互
-
AI数据流：
- 设计AI模型的输入输出数据结构
- 设计AI模型的训练和推理流程
- 设计AI结果的处理和存储方案
第五步：设计部署架构
-
开发环境部署：
- 设计开发环境的配置和依赖
- 设计开发环境的启动和调试方案
-
测试环境部署：
- 设计测试环境的配置和依赖
- 设计测试环境的部署和测试方案
-
生产环境部署：
- 设计生产环境的配置和依赖
- 设计生产环境的部署和监控方案
- 设计生产环境的扩展性和容错方案
第六步：编写架构设计文档
-
文档结构设计：
- 设计架构设计文档的结构，包含技术栈、模块划分、数据流、部署架构等章节
-
文档内容编写：
- 根据收集的信息，编写架构设计文档内容
- 确保文档内容完整、清晰、准确
- 使用图表和示例辅助说明
-
文档保存：
- 将架构设计文档保存至
/项目文档/启动文档/架构设计文档.md - 与用户确认文档内容，确保符合其要求
- 将架构设计文档保存至
5. 执行建议
- 深入了解：仔细分析项目的目录结构、文档和代码，确保对项目有全面的理解
- 系统性思考：从整体架构出发，系统性地设计技术栈、模块划分、数据流和部署架构
- 模块化设计：采用模块化设计思想，确保各个模块职责清晰、接口明确
- 数据流清晰：设计清晰的数据流，确保数据在各个模块间的传递顺畅
- 部署合理：根据项目特点，设计合理的部署架构，确保系统的稳定性和可扩展性
- 文档详细：编写详细的架构设计文档，使用图表和示例辅助说明，确保文档易于理解
- 与用户沟通：与用户保持深度沟通，确保架构设计符合用户的需求和期望
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 · 158 lines · 26 tokens per session scan A 5c9adde6a7ed
vibe-architecture is a skill published in the GitHub repository xushuodasd/VIBE-Claude-Plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 1,739 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to smart-search, differing in 243 lines, and is treated as a copy.
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…