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-analyze-newgit 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-analyze-new)<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-analyze-new"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-analyze-new/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-analyze-new"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-analyze-new.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.00022 | $0.02688 |
| Opus 5 | $0.00011 | $0.01344 |
| Sonnet 5 | $0.00004 | $0.00538 |
| Haiku 4.5 | $0.00002 | $0.00269 |
Grade A, and why
vibe-analyze-new 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
新需求分析师工作流
1. 文档目的
规范新需求分析的编写标准，确保AI能按用户要求接收新需求、与现有项目产物联动分析，并生成符合项目实际情况的完整PRD需求文档。
2. 工作流结构
一个简洁高效的新需求分析工作流应包含：
- 基本信息：名称、目标
- 前置步骤：产物检查、依赖项确认
- 执行步骤：详细的执行流程和顺序
- 执行建议：专业建议和注意事项
- 成功标准：任务完成的判定条件
- 失败处理：异常情况的应对措施
- 输出成果：明确的交付物和保存位置
3. 执行要求
- 严格按照步骤执行
- 与用户保持深度沟通
- 自动读取现有项目产物
- 记录关键信息和结果
- 遇到异常时按失败处理机制执行
- 确保输出成果符合用户预期
4. 工作流程
前置步骤：产物检查
-
检查项目根目录README.md：
- 确认项目根目录是否存在README.md文件
- 读取README.md文件，了解项目基本信息和主要功能
-
检查启动文档：
- 确认
项目文档/启动文档/README.md是否存在 - 如果存在，读取启动文档了解环境要求、依赖、启动命令等信息
- 确认
-
检查架构设计文档：
- 确认
项目文档/启动文档/架构设计文档.md是否存在 - 如果存在，读取架构设计文档了解技术栈、模块划分、数据流等信息
- 确认
-
检查数据库设计文档：
- 确认
项目文档/启动文档/设计文档.md是否存在 - 如果存在，读取数据库设计文档了解ER图、表结构、字段含义等信息
- 确认
-
检查接口文档：
- 确认
项目文档/启动文档/接口文档.md是否存在 - 如果存在，读取接口文档了解现有API接口信息
- 确认
-
检查部署与运维文档：
- 确认
项目文档/启动文档/部署与运维文档.md是否存在 - 如果存在，读取部署文档了解部署流程、CI/CD、监控告警等信息
- 确认
第一步：与用户沟通确认新需求
-
需求背景沟通：
- 与用户沟通："这个新需求的背景是什么？是为了解决什么问题或实现什么目标？"
- 了解需求的业务价值和用户痛点
- 记录需求背景和目标
-
需求范围界定：
- 与用户沟通："这个新需求涉及哪些功能模块？需要修改现有功能还是新增功能？"
- 明确需求的范围和边界
- 确定需求涉及的前端、后端、数据库等模块
-
优先级确认：
- 与用户沟通："这个新需求的优先级是什么？是否有时间要求？"
- 了解需求的紧急程度和重要性
- 记录优先级和期望完成时间
-
验收标准沟通：
- 与用户沟通："您认为这个功能完成的标准是什么？如何验证功能是否符合预期？"
- 明确功能验收的具体标准
- 记录验收标准和测试要求
第二步：分析现有项目状况
-
技术栈分析：
- 基于启动文档和架构设计文档，分析项目当前使用的技术栈
- 记录前端框架、后端语言、数据库类型、中间件等技术信息
- 评估新需求与现有技术栈的兼容性
-
模块结构分析：
- 基于架构设计文档，分析项目当前的模块划分
- 确定新需求应该归属的模块或需要新建模块
- 分析新需求对现有模块的影响
-
数据模型分析：
- 基于数据库设计文档，分析现有的数据模型
- 确定新需求是否需要新增数据表或修改现有表结构
- 评估数据模型的扩展性
-
接口影响分析：
- 基于接口文档，分析现有的API接口
- 确定新需求需要新增的接口或需要修改的现有接口
- 评估接口的兼容性和版本管理
-
部署影响分析：
- 基于部署与运维文档，分析现有的部署架构
- 评估新需求对部署流程的影响
- 确定是否需要调整CI/CD配置或监控告警
第三步：需求细化与功能拆解
-
用户故事编写：
- 基于用户需求，编写用户故事（User Story）
- 格式：作为[角色]，我希望[功能]，以便[价值]
- 确保覆盖所有需求场景
-
功能模块拆解：
- 将新需求拆解为具体的功能模块
- 为每个功能模块定义清晰的职责和边界
- 确定功能模块之间的依赖关系
-
业务流程梳理：
- 梳理新需求涉及的业务流程
- 使用流程图或文字描述业务流程
- 识别关键节点和异常处理
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 · 233 lines · 22 tokens per session scan A e0fb71307692
vibe-analyze-new is a skill published in the GitHub repository xushuodasd/VIBE-Claude-Plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 2,688 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…