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-bug-trackergit 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-bug-tracker)<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-bug-tracker"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-bug-tracker/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-bug-tracker"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-bug-tracker.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.00021 | $0.01716 |
| Opus 5 | $0.00010 | $0.00858 |
| Sonnet 5 | $0.00004 | $0.00343 |
| Haiku 4.5 | $0.00002 | $0.00172 |
Grade A, and why
vibe-bug-tracker 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
线上问题记录与历史Bug清单工作流
1. 基本信息
- 名称：线上问题记录与历史Bug清单工作流
- 目标：全面了解和记录项目的线上问题、历史Bug、常见坑、历史故障和性能瓶颈，为项目的稳定运行和持续改进提供参考
2. 前置步骤
产物检查
-
检查项目结构：
- 确认项目的基本结构和技术栈
- 检查是否存在现有的问题记录或Bug追踪系统
-
检查相关文档：
- 检查是否有现有的问题记录文档
- 检查是否有Bug追踪工具的使用记录
- 检查是否有性能分析报告
依赖项确认
-
技术栈确认：
- 确认前端、后端使用的技术栈
- 确认数据库类型和版本
- 确认部署环境和相关服务
-
工具确认：
- 确认是否使用了Bug追踪工具（如Jira、GitHub Issues等）
- 确认是否使用了监控和日志分析工具
- 确认是否有性能测试工具的使用记录
3. 执行步骤
第一步：项目全面分析
-
技术架构分析：
- 了解项目的整体架构
- 识别核心组件和服务
- 了解各组件间的依赖关系
-
历史问题收集：
- 查阅Bug追踪系统中的历史记录
- 查看项目的版本发布记录和变更日志
- 收集团队成员的经验反馈
-
线上环境分析：
- 了解生产环境的配置和部署情况
- 检查监控系统的历史数据
- 分析日志系统中的错误记录
第二步：问题分类与整理
-
Bug分类：
- 按功能模块分类
- 按严重程度分类
- 按发生频率分类
- 按影响范围分类
-
故障分析：
- 记录历史故障的发生时间和持续时间
- 分析故障的根本原因
- 记录故障的解决方案和恢复时间
- 评估故障的影响程度
-
性能瓶颈识别：
- 分析系统性能数据
- 识别CPU、内存、磁盘、网络等资源瓶颈
- 分析数据库性能问题
- 识别代码层面的性能问题
-
常见坑总结：
- 记录开发和部署过程中的常见问题
- 总结容易出错的配置和操作
- 整理常见错误的解决方案
第三步：详细信息收集
-
Bug详情记录：
- 记录Bug的具体表现和复现步骤
- 记录Bug的发现时间和修复时间
- 记录Bug的修复方案和验证结果
- 记录Bug的影响范围和严重程度
-
故障详情记录：
- 记录故障的具体现象和影响范围
- 记录故障的排查过程和使用的工具
- 记录故障的解决方案和预防措施
- 记录故障的事后分析和改进建议
-
性能问题记录：
- 记录性能问题的具体表现和测试数据
- 记录性能优化的方案和实施结果
- 记录性能监控的关键指标和阈值
- 记录性能问题的预防措施
-
常见坑记录：
- 记录常见坑的具体场景和表现
- 记录避免和解决这些问题的方法
- 记录相关的最佳实践和注意事项
第四步：文档编写与整合
-
文档结构设计：
- 设计问题记录文档的结构
- 确定章节划分和内容组织方式
-
内容编写：
- 按照分类和整理的结果编写详细内容
- 确保内容完整覆盖所有收集到的信息
- 提供清晰的问题描述和解决方案
-
文档审核：
- 内容准确性检查
- 信息完整性检查
- 格式规范检查
- 与团队成员的交叉验证
4. 执行建议
- 深入调研：在编写文档前，充分了解项目的历史和现状，收集尽可能多的信息
- 系统分析：采用系统化的方法分析问题，确保不遗漏任何重要信息
- 注重细节：详细记录每个问题的具体情况和解决方案，确保文档的实用性
- 客观记录：保持客观中立的态度，准确记录问题的真实情况
- 持续更新：问题记录文档应随着项目的发展定期更新，及时添加新发现的问题
- 团队协作：与项目团队保持沟通，确保记录的信息准确无误
- 总结规律：从历史问题中总结规律，为未来的开发和运维提供参考
- 预防为主：基于历史问题，提出预防措施，减少类似问题的发生
5. 成功标准
- 文档完整覆盖项目的线上问题、历史Bug、常见坑、历史故障和性能瓶颈
- 文档内容准确反映项目的实际情况和历史问题
- 文档格式规范，结构清晰，易于理解和使用
- 文档包含详细的问题描述、根本原因分析和解决方案
- 文档保存至指定位置：
/项目文档/启动文档/问题记录.md - 文档对项目的持续改进和问题预防具有参考价值
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 · 159 lines · 21 tokens per session scan A e90601a20892
vibe-bug-tracker is a skill published in the GitHub repository xushuodasd/VIBE-Claude-Plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,716 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
error-handling
Handle failures deliberately — fail loud, recover narrow, never swallow.
incident-response
When production is broken — stop the bleeding first, diagnose second, learn third.
issue-triage
Turn a vague report into a clear, reproducible, prioritized issue.
observability-and-logging
Instrument code so failures are diagnosable in production, without noise.
performance-profiling
Make it fast by measuring first — never optimize on a guess.
systematic-debugging
Reproduce, isolate the root cause, fix the cause not the symptom, then prove it.