agentmods.dev

vibe-stage-update

vibe-stage-update is a skill for Claude Code from xushuodasd/VIBE-Claude-Plugin. It costs 22 tokens per session (1,074 once invoked), scanned A, original, MIT.

A workflow for moving a software project from one development stage to the next. It checks that frontend and backend work are aligned, updates the stage file, and records the change.

In plain words
What is it for?
Use it after a development stage to check completion, update the next stage, verify the result, and create a written update record.
Why use it?
It prevents the project status from advancing before the required work is complete and keeps planning documents consistent.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the vibe-claude-plugin plugin — 25 skills, 1 command shipped together

not rated 4repo 2mo ago A scan 22 tokens original MIT

Good fit Use it after a development stage to check completion, update the next stage, verify the result, and create a written update record.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xushuodasd/vibe-claude-plugin/vibe-stage-update
View source ↗ xushuodasd/VIBE-Claude-Plugin
Install

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.

Any agent
npx skills add xushuodasd/VIBE-Claude-Plugin --skill vibe-stage-update
Clone the repo
git clone --depth 1 https://github.com/xushuodasd/VIBE-Claude-Plugin

Made for: Claude Code.

Or install vibe-claude-plugin, the plugin that ships this one along with the rest of its 25 skills, 1 command.

Wrote 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.

agentmods badge for vibe-stage-update

README.md
[![agentmods](https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-stage-update/github.svg)](https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-stage-update)
Your own site
<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-stage-update"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-stage-update/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.

agentmods 80×15 button for vibe-stage-update

Your own site · 80×15
<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-stage-update"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-stage-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,074 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.01074
Opus 5 $0.00011 $0.00537
Sonnet 5 $0.00004 $0.00215
Haiku 4.5 $0.00002 $0.00107

Measured 11d ago against content hash 78b1a787a257, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

vibe-stage-update 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.

skills/vibe-stage-update/SKILL.md · 101 lines

What it actually says

阶段更新工作流

1. 文档目的

规范项目开发阶段的更新流程，确保在当前阶段完成后能够及时更新开发阶段标识，为后续开发工作提供明确的指导。

2. 工作流结构

一个完整的阶段更新工作流应包含：

  • 基本信息：名称、目标
  • 前置步骤：阶段完成检查、依赖项确认
  • 执行步骤：详细的执行流程和顺序
  • 执行建议：专业建议和注意事项
  • 成功标准：任务完成的判定条件
  • 失败处理：异常情况的应对措施
  • 输出成果：明确的交付物和保存位置

3. 执行要求

  • 严格按照步骤执行
  • 与用户保持深度沟通
  • 记录关键信息和结果
  • 遇到异常时按失败处理机制执行
  • 确保输出成果符合用户预期

4. 文档管理

  • 执行后根据实际情况更新文档
  • 进行版本管理，确保使用最新版本

工作流程

前置步骤：阶段完成检查

  1. 检查前端阶段完成情况：

    • 查看./frontend/doc/阶段日志.md文件
    • 确认前端是否已完成当前阶段的开发任务

  2. 检查后端阶段完成情况：

    • 查看./backend/doc/阶段日志.md文件
    • 确认后端是否已完成当前阶段的开发任务

  3. 阶段对齐检查：

    • 确保前端和后端都已完成当前阶段的开发任务
    • 如果前后端阶段不一致，提示用户先完成未完成的阶段

第一步：读取当前开发阶段

  1. 读取 stage.md 文件：

    • 读取./.vibe/stage.md文件
    • 确定当前项目的开发阶段

  2. 读取开发计划文档：

    • 读取./.vibe/docs/plan/overview.md
    • 了解项目整体的阶段划分和顺序

第二步：更新开发阶段

  1. 阶段更新：

    • 根据项目阶段开发计划总览文档中的阶段顺序，确定当前阶段的下一阶段
    • 将当前阶段更新为下一阶段
    • 保持文件的其他内容不变

  2. 验证更新：

    • 确认文件已成功更新
    • 验证新的阶段信息是否正确

第三步：文档化

  1. 更新记录：
    • 在./.vibe/docs/plan/目录下创建阶段更新记录
    • 记录阶段更新的时间、原因和相关信息

执行建议

  1. 阶段完成确认：在执行本工作流前，确保前后端都已完成当前阶段的所有任务
  2. 文档同步：确保阶段日志和开发计划文档与实际开发进度保持同步
  3. 谨慎操作：更新阶段信息时要谨慎，确保参考项目阶段开发计划总览文档确定下一阶段
  4. 及时通知：阶段更新后，及时通知相关开发人员
  5. 版本控制：对 stage.md 文件进行版本控制，保留历史记录
  6. 文档参考：严格参考项目阶段开发计划总览文档中的阶段顺序进行更新

成功标准

  1. 确认前后端都已完成当前阶段的开发任务
  2. 成功更新 stage.md 文件中的开发阶段信息
  3. 根据项目阶段开发计划总览文档正确确定并更新到下一阶段
  4. 生成阶段更新记录文档
  5. 为后续开发工作提供明确的阶段指导

失败处理

  1. 阶段未完成：如果前后端任何一方未完成当前阶段，暂停工作流，待完成后再继续
  2. 文件不存在：如果必要的文件不存在，先创建文件或提示用户创建
  3. 更新失败：如果更新 stage.md 文件失败，检查文件权限并重新尝试
  4. 文档不一致：如果项目阶段开发计划总览文档与当前阶段信息不一致，提示用户检查文档

输出成果

  1. 更新后的 stage.md 文件 - 保存至./.vibe/stage.md
  2. 阶段更新记录 - 保存至./.vibe/docs/plan/stage-update-log.md

记住，及时更新开发阶段信息对于项目的顺利进行至关重要。通过本工作流的执行，确保项目开发阶段的准确标识，为后续开发工作提供清晰的指导。

Changes

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.

  1. 11d ago First seen · 101 lines · 22 tokens per session scan A 78b1a787a257

Subscribe to this mod's changes

vibe-stage-update 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 1,074 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.

Claude CodeProject managementai-agentai-workflowautonomous-codingclaude-plugincoding-agent
Related

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.

skullninja/coco-workflow · 26 tokens

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.

skullninja/coco-workflow · 36 tokens

status

Check one or more Agrenting remote-agent hirings, answer agent questions, and retrieve completed output or artifacts. Use when the user asks about hiring progress, remote tasks, job status, questions, results, or artifacts.

zaalipro/llmotions-agentfarm-claude-plugins · 46 tokens

gh-file-issue

Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.

Hmbown/CodeWhale · 41 tokens

gh-treasure-hunt

Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.

Hmbown/CodeWhale · 39 tokens

speckit-workflow

Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.

tzachbon/smart-ralph · 30 tokens