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-frameworkgit 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-framework)<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-framework"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-framework/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-framework"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-framework.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.00020 | $0.01925 |
| Opus 5 | $0.00010 | $0.00962 |
| Sonnet 5 | $0.00004 | $0.00385 |
| Haiku 4.5 | $0.00002 | $0.00193 |
Grade A, and why
vibe-framework 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 10d 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.
框架设计工作流
1. 文档目的
规范项目框架设计的流程，确保AI能按用户要求设计出稳定、可用、高可扩展的技术框架。
2. 工作流结构
一个简洁高效的框架设计工作流应包含：
- 基本信息：项目名称、设计目标
- 前置步骤：文档检查、依赖项确认
- 执行步骤：详细的框架设计流程和顺序
- 执行建议：专业建议和注意事项
- 成功标准：框架设计完成的判定条件
- 失败处理：异常情况的应对措施
- 输出成果：明确的交付物和保存位置
5. 成功标准
- 框架设计文档完整，包含所有必要的设计内容
- 框架设计符合高性能、高可靠性、易于扩展和维护的要求
- 框架设计与需求文档和技术文档的要求一致
- 框架实现计划和测试方案完整可行
6. 失败处理
- 如果需求文档或技术文档不存在，自动执行项目需求分析工作流
- 如果框架设计过程中遇到技术难题，记录问题并寻求解决方案
- 如果框架设计不符合要求，重新进行设计直到满足标准
- 如果遇到其他异常情况，记录问题并采取相应的应对措施
3. 执行要求
- 严格按照步骤执行
- 记录关键信息和结果
- 遇到异常时按失败处理机制执行
- 确保输出成果符合文档要求
4. 文档管理
- 执行后根据实际情况更新文档
- 进行版本管理，确保使用最新版本
工作流程
前置步骤：文档检查
-
检查需求文档：
- 确认
./项目文档/需求文档/目录下是否存在PDR需求文档 - 如果不存在，自动执行项目需求分析工作流
- 确认
-
检查技术文档：
- 确认
./项目文档/技术文档/目录下是否存在技术方案设计文档 - 如果不存在，自动执行项目需求分析工作流
- 确认
-
读取相关文档：
- 读取PDR需求文档，了解项目的功能需求、非功能需求和技术栈偏好
- 读取技术方案设计文档，了解技术栈选择、架构设计和关键技术点
第一步：框架设计目标确定
-
设计目标确认：
- 默认追求高性能、高可靠性、易于扩展和维护的系统架构
- 明确框架设计的核心目标和优先级
-
技术约束确认：
- 根据需求文档和技术文档，确定技术栈的选择范围和限制
- 确认框架设计的技术边界
-
扩展性需求确认：
- 根据需求文档，分析系统未来可能需要扩展的功能
- 确定框架需要支持的扩展场景
第二步：框架架构设计
-
整体架构设计：
- 基于需求文档和技术文档，设计系统的整体架构
- 确定系统的层次结构和模块划分
- 设计系统的核心流程和数据流
-
模块设计：
- 详细设计每个模块的功能和职责
- 确定模块之间的接口和依赖关系
- 设计模块的内部结构和实现方式
-
技术选型：
- 确认技术栈的具体版本和配置
- 选择适合的框架和库
- 评估技术选型的可行性和风险
第三步：稳定性设计
-
错误处理机制：
- 设计完善的错误处理和异常捕获机制
- 确保系统在遇到错误时能够优雅降级
- 实现错误日志和监控机制
-
容错设计：
- 设计系统的容错机制，确保单点故障不会影响整个系统
- 实现系统的冗余和备份方案
- 设计系统的恢复机制
-
性能优化：
- 分析系统的性能瓶颈
- 设计性能优化方案，确保系统的响应速度和吞吐量
- 实现性能监控和调优机制
第四步：可用性设计
-
用户体验设计：
- 设计系统的用户界面和交互流程
- 确保系统的操作简单直观
- 实现用户反馈和帮助机制
-
系统可靠性：
- 设计系统的可靠性保障机制
- 确保系统的稳定性和可用性
- 实现系统的监控和告警机制
-
部署和运维：
- 设计系统的部署方案
- 实现系统的自动化运维机制
- 设计系统的升级和回滚方案
第五步：高可扩展性设计
-
模块化设计：
- 设计高度模块化的系统结构
- 确保模块之间的低耦合和高内聚
- 实现模块的插件化和可配置化
-
扩展性机制：
- 设计系统的扩展点和扩展机制
- 确保系统能够方便地添加新功能和模块
- 实现系统的动态配置和热加载
-
兼容性设计：
- 设计系统的版本兼容性机制
- 确保系统能够平滑升级和迁移
- 实现系统的向后兼容性
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.
- 10d ago First seen · 174 lines · 20 tokens per session scan A 034155e8359b
vibe-framework is a skill published in the GitHub repository xushuodasd/VIBE-Claude-Plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 1,925 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…