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-databasegit 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-database)<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-database"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-database/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-database"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-database.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.00018 | $0.01566 |
| Opus 5 | $0.00009 | $0.00783 |
| Sonnet 5 | $0.00004 | $0.00313 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
vibe-database 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 9d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
数据库设计文档工作流
1. 文档目的
规范数据库设计文档的编写标准,确保AI能按照项目实际情况,生成包含ER图、表含义、字段含义、索引、关联关系的完整数据库设计文档。
2. 工作流结构
一个简洁高效的数据库设计文档工作流应包含:
- 基本信息:名称、目标
- 前置步骤:产物检查、依赖项确认
- 执行步骤:详细的执行流程和顺序
- 执行建议:专业建议和注意事项
- 成功标准:任务完成的判定条件
- 失败处理:异常情况的应对措施
- 输出成果:明确的交付物和保存位置
3. 执行要求
- 严格按照步骤执行
- 与用户保持深度沟通
- 记录关键信息和结果
- 遇到异常时按失败处理机制执行
- 确保输出成果符合用户预期
4. 工作流程
前置步骤:产物检查
-
检查项目根目录README.md:
- 确认项目根目录是否存在README.md文件
- 读取README.md文件,了解项目基本信息和主要功能
-
检查项目目录结构:
- 查看项目的完整目录结构
- 确认是否存在配置文件、依赖文件等
-
检查项目文档:
- 查看
doc/目录下的工作流程文档 - 了解项目的开发规范和工作流程
- 查看
-
检查是否存在数据库相关文档:
- 检查项目中是否存在数据库设计文档
- 检查项目中是否存在数据模型文件
- 检查项目中是否存在数据库迁移文件
第一步:了解项目需求
-
分析项目README:
- 理解项目的定位、目标和主要功能
- 识别项目的核心业务逻辑
-
分析项目目录结构:
- 分析
.vibe/目录下的开发规则 - 分析
doc/目录下的工作流程文档 - 理解项目的组织方式和设计思路
- 分析
-
识别项目技术栈:
- 检查项目中是否存在package.json、requirements.txt等依赖文件
- 分析项目中使用的编程语言、框架和库
- 识别项目中使用的数据库类型
第二步:分析项目代码
-
检查后端代码:
- 检查项目中是否存在后端代码目录
- 分析后端代码中的数据模型定义
- 分析后端代码中的数据库操作
-
检查前端代码:
- 检查项目中是否存在前端代码目录
- 分析前端代码中的数据结构
- 分析前端代码中的API调用
-
检查配置文件:
- 检查项目中的配置文件,了解数据库连接信息
- 检查项目中的环境变量配置
第三步:设计数据库架构
-
识别实体:
- 基于项目功能,识别核心实体
- 确定每个实体的属性和关系
-
设计表结构:
- 为每个实体设计对应的表结构
- 确定表的字段名称、数据类型、长度、约束等
- 设计表的主键、外键和索引
-
设计关系:
- 设计实体间的关联关系
- 确定关系的类型(一对一、一对多、多对多)
- 设计关系的实现方式
第四步:生成ER图
-
设计ER图结构:
- 确定ER图的布局和样式
- 设计实体的表示方式
- 设计关系的表示方式
-
绘制ER图:
- 使用Mermaid或其他工具绘制ER图
- 确保ER图清晰、准确地表示实体和关系
第五步:编写数据库设计文档
-
文档结构设计:
- 设计数据库设计文档的结构,包含ER图、表含义、字段含义、索引、关联关系等章节
-
文档内容编写:
- 编写ER图的说明和解释
- 编写每个表的含义和用途
- 编写每个字段的含义和约束
- 编写索引的设计和用途
- 编写关联关系的设计和实现
-
文档保存:
- 将数据库设计文档保存至
/项目文档/启动文档/设计文档.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.
- 9d ago First seen · 144 lines · 18 tokens per session scan A c47464638dbc
vibe-database is a skill published in the GitHub repository xushuodasd/VIBE-Claude-Plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,566 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
database-migrations
Change a schema safely on a live system — reversible, ordered, zero-downtime.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…