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-file-listgit 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-file-list)<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-file-list"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-file-list/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-file-list"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-file-list.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.00017 | $0.01061 |
| Opus 5 | $0.00009 | $0.00531 |
| Sonnet 5 | $0.00003 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
vibe-file-list 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VIBE 框架文件清单
路径约定说明：所有 VIBE 框架管理的文档统一存放在项目根目录下的
.vibe/目录中，便于与 Claude Code 的.claude/目录区分。
1. 状态与启动文件 (.vibe/)
.vibe/stage.md- 当前项目开发阶段文件（由 vibe-stage-update 维护）.vibe/startup.md- 项目启动工作流文件.vibe/tasks.md- 任务清单（autopilot 引擎的"状态机"，由 vibe-plan 初始化）
2. 工作流程文档 (.vibe/workflows/)
所有工作流定义文档统一存放在此目录。
2.1 需求与设计类
analyze-req.md- 项目需求分析流程architecture.md- 架构设计流程database.md- 数据库设计流程api-rules.md- API 规则文档设计流程
2.2 计划与检查类
plan.md- 项目阶段开发计划流程review.md- 代码检查流程integrate.md- 前后端代码对接流程meta.md- AI 工作流制作流程（用于自举新工作流）
2.3 开发执行类
frontend.md- 前端开发流程backend.md- 后端开发流程stage-update.md- 阶段更新流程test.md- 测试与质量门禁流程security.md- 安全审查流程ui-design.md- UI 设计系统流程ui-beautify.md- UI 美化与动效流程
3. 项目文档 (.vibe/docs/)
3.1 需求文档 (docs/requirements/)
prd.md- 产品需求文档（Product Requirements Document）
3.2 技术文档 (docs/technical/)
architecture.md- 系统架构设计文档api-rules.md- API 设计规则文档api-spec.md- API 设计规范文档
3.3 开发计划 (docs/plan/)
overview.md- 项目阶段开发计划总览frontend.md- 前端开发计划backend.md- 后端开发计划review-report.md- 代码检查问题报告
3.4 报告 (docs/reports/)
test/- 测试报告security/- 安全审查报告design/- 设计系统文档motion/- 动效清单
4. API 相关文件
API表.md- API 端点清单（项目根）API规范表.md- API 设计规范表（项目根）
5. 开发手册
frontend/doc/README.md- 前端开发指南backend/doc/README.md- 后端开发指南
6. 项目架构文档
.vibe/docs/technical/architecture.md- 项目整体架构设计文档
7. 其他文件
README.md- 项目说明文件（项目根）LICENSE- 许可证文件（项目根）package.json/requirements.txt/go.mod等依赖文件
路径迁移说明
本文件由旧版 doc/workflaw/、doc/workfile/、doc/wroktwo/、doc/项目文档/ 体系迁移到 .vibe/ 统一目录。迁移映射：
| 旧路径 | 新路径 |
|---|---|
.trae/rules/kaifa.md |
.vibe/stage.md |
.trae/rules/kaifa1.md |
.vibe/startup.md |
doc/workflaw/* |
.vibe/workflows/* |
doc/workfile/* |
.vibe/workflows/* |
doc/wroktwo/* |
.vibe/workflows/* |
doc/项目文档/需求文档/ |
.vibe/docs/requirements/ |
doc/项目文档/技术文档/ |
.vibe/docs/technical/ |
doc/项目文档/开发计划/ |
.vibe/docs/plan/ |
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 · 91 lines · 17 tokens per session scan A 84697bafbedb
vibe-file-list is a skill published in the GitHub repository xushuodasd/VIBE-Claude-Plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,061 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…