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 chentao326/vibe-code --skill vibe-statusgit clone --depth 1 https://github.com/chentao326/vibe-codeWrote 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/chentao326/vibe-code/vibe-status)<a href="https://agentmods.dev/skills/chentao326/vibe-code/vibe-status"><img src="https://agentmods.dev/badge/skills/chentao326/vibe-code/vibe-status/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/chentao326/vibe-code/vibe-status"><img src="https://agentmods.dev/badge/skills/chentao326/vibe-code/vibe-status.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.00063 | $0.00986 |
| Opus 5.5 | $0.00025 | $0.00394 |
| Sonnet 5.5 | $0.00013 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
vibe-status 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 1mo 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.
What it actually says
vibe-status — 状态看板
只读，无副作用。任何时候都可以调用。
工作流
Phase 1: 读取 state + handoff 阶段
- 读
.vibe-state.json所有字段 - 检测 handoff 阶段：
ls handoff/*.json 2>/dev/null || echo "NO_FILES"
- 将 handoff 阶段与 vibe 校准数据合并渲染
Phase 2: 渲染看板
输出格式：
📊 Vibe Code — 状态看板
Rubric: v0 | 校准池: 5 samples | Confidence: 🟡 偏低
---
📝 WIP（进行中）
• tasks/fix-auth.md — assessed 2026-05-24
⏰ 待复盘（共 2 个）
• predictions/fix-auth.md — overdue（完成于 2026-05-22）
• predictions/add-cache.md — ready
📈 统计
总评估: 8 | 已完成: 5 | 已放弃: 1 | 准确率趋势: ↗ 上升
⚠️ 提醒
• 校准池 5 个样本，可以考虑 bump 升级模型
• 2 个任务待复盘，建议先复盘再评估新任务
Handoff 状态（融合协议）
根据 handoff-vibe-bridge.md 同步显示 handoff 阶段。
检测命令
ls handoff/*.json 2>/dev/null || echo "NO_FILES"
阶段展示
| 信号文件 | 展示 |
|---|---|
| (无) | 🔵 Init — "等待写 spec" |
plan-ready.json |
🟡 Plan Ready — "等待编码" |
build-done.json |
🟢 Build Done — "等待 review / 可以复盘" |
review-fixes.json |
🟠 Fixes Needed — "等待修复" |
polish-done.json |
🟡 Polish Done — "等待重审" |
review-passed.json |
🟢 Review Passed — "等待提交" |
committed.json |
✅ Done — "已完成" |
看板展示格式
## 🔄 Handoff 状态
模式: codex-self-handoff
阶段: build-done → 等待 review
Feature: post-review-fixes
## 📊 Vibe 校准
Rubric: v1 | 校准池: 6 | Confidence: 🟢 中
（后续跟现有 vibe 看板内容）
自动检测项
| 检测 | 条件 | 提醒 |
|---|---|---|
| Bump 建议 | calibration_samples ≥5 + 未 bump 过 | "可以考虑升级模型" |
| 复盘积压 | pending_retros ≥3 | "建议先复盘再评估新任务" |
| 偏差警告 | consecutive_directional_errors ≥3 | "连续3次同向偏差，rubric可能系统性不准" |
| 自评分警告 | last_assessment_self_scored == true | "上次评估没有走 blind sub-agent" |
| WIP 积压 | wip_tasks ≥5 | "建议先完成已有任务" |
| Rubric 健康 | rubric.md 行数 >500 | "rubric.md 可能需要清理" |
信心等级展示
| calibration_samples | 展示 |
|---|---|
| 0 | 🔴 极低 — "占星级别，纯纪律训练" |
| 1-2 | 🟠 低 — "方向感优于绝对数字" |
| 3-5 | 🟡 偏低 — "可作为参考之一" |
| 6-10 | 🟢 中 — "可参与决策" |
| 11+ | 🔵 高 — "值得信赖" |
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.
- 1mo ago First seen · 110 lines · 63 tokens per session scan A 9367528a81ca
vibe-status is a skill published in the GitHub repository chentao326/vibe-code (2 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 986 once invoked, about $0.0003 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.