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 timurgaleev/vibestack --skill vibe-upgradegit clone --depth 1 https://github.com/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/vibe-upgrade)<a href="https://agentmods.dev/skills/timurgaleev/vibestack/vibe-upgrade"><img src="https://agentmods.dev/badge/skills/timurgaleev/vibestack/vibe-upgrade/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/timurgaleev/vibestack/vibe-upgrade"><img src="https://agentmods.dev/badge/skills/timurgaleev/vibestack/vibe-upgrade.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.00045 | $0.04081 |
| Opus 5 | $0.00023 | $0.02041 |
| Sonnet 5 | $0.00009 | $0.00816 |
| Haiku 4.5 | $0.00005 | $0.00408 |
Grade C, and why
vibe-upgrade scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
git clone --depth 1 https://github.com/timurgaleev/vibestack.git "$TMP_DIR/vibestack" || { echo "CLONE_FAILED"; rm -rf "$TMP_DIR"; exit 0; } How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to invoke
Use when asked to "upgrade", "update vibestack", "get the latest skills", or
after vibe-update-check reports a newer version is available (a preamble that
sees UPDATE: in the update-check output runs the Inline upgrade flow below;
a direct /vibe-upgrade runs Standalone usage).
/vibe-upgrade — Update vibestack to the latest release
Claude Code ships a built-in /upgrade, so this skill stays namespaced as
/vibe-upgrade. Binaries live in ~/.vibestack/bin/ (vibe-config,
vibe-update-check) and mutable state lives under ~/.vibestack/.
Inline upgrade flow
This section is referenced by skill preambles when they detect an available
update (UPDATE: line from vibe-update-check).
Step 1: Ask the user (or auto-upgrade)
First, check whether auto-upgrade is enabled:
_AUTO=""
[ "${VIBESTACK_AUTO_UPGRADE:-}" = "1" ] && _AUTO="true"
[ -z "$_AUTO" ] && _AUTO=$(~/.vibestack/bin/vibe-config get auto_upgrade 2>/dev/null || true)
echo "AUTO_UPGRADE=$_AUTO"
If AUTO_UPGRADE=true or AUTO_UPGRADE=1: Skip the question. Log
"Auto-upgrading vibestack v{old} → v{new}..." and proceed directly to Step 2.
The upgrade blocks in Step 4 roll back automatically if ./install fails during
an auto-upgrade — if that happens, warn the user: "Auto-upgrade failed — restored
the previous version. Run /vibe-upgrade manually to retry."
Otherwise, use AskUserQuestion:
- Question: "vibestack v{new} is available (you're on v{old}). Upgrade now?"
- Options: ["Yes, upgrade now", "Always keep me up to date", "Not now", "Never ask again"]
If "Yes, upgrade now": Proceed to Step 2.
If "Always keep me up to date":
~/.vibestack/bin/vibe-config set auto_upgrade true
Tell the user: "Auto-upgrade enabled. Future updates install automatically." Then proceed to Step 2.
If "Not now": Write a snooze marker with escalating backoff (first snooze = 24h, second = 48h, third+ = 1 week), then continue with the skill the user originally invoked. Do not mention the upgrade again this session.
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 · 357 lines · 45 tokens per session scan C d46e9a8d8045
vibe-upgrade is a skill published in the GitHub repository timurgaleev/vibestack (6 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 4,081 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
grok-build-supervisor
Initialize the persistent local proxy, then immediately ensure a visible Grok Build TUI for the current workspace when /grokexecute on activates, and continuously supervise that coding-agent session through a user-level Supervisor daemon as the user sends work, waits for completion, reconnects from another host task…
cursor-delegate
Delegate bounded light-to-medium implementation, investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns direction and risk boundaries. Also use when the user explicitly asks to create, keep, continue, inspect, or close the same Cursor execution session…
grok-executor-mode
Explicit Grok executor on/off control and task-local execution policy. Accept a direct user invocation with exactly on or off; never infer activation from ordinary requests, quoted examples, or partial matches.
grok-executor-off
Explicitly disable Grok executor mode for this task without cancelling work or closing its terminal. Select this skill directly; no argument is required.
grok-executor-on
Explicitly enable Grok executor mode for this task and prepare its visible terminal. Select this skill directly; no argument is required.
bedrock-agentcore
Deploy and operate agents on Amazon Bedrock AgentCore — Runtime, Harness, Memory, Identity, and Observability. Use when hosting an agent on AWS, containerising an agent for AgentCore Runtime, wiring session or long-term memory, or choosing between Harness, Runtime, and plain Lambda.