What is version-checker?

A project consistency checker for a command-line and MCP software project. It compares versions, test counts, tool and provider counts, documentation, and install links across the codebase.

Use it to check package versions, documented test totals, command and provider counts, hardcoded version text, and installation URLs across project files.

It finds information that has become out of sync after releases, version changes, command changes, or documentation edits. This helps prevent users and developers from seeing conflicting details.

How vericontext/vibeframe configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to vericontext/vibeframe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/vericontext/vibeframe/main/.claude/agents/version-checker.md

Clone the repo

git clone --depth 1 https://github.com/vericontext/vibeframe

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/vericontext/vibeframe/version-checker/github.svg)](https://agentmods.dev/agents/vericontext/vibeframe/version-checker)

Your own site

<a href="https://agentmods.dev/agents/vericontext/vibeframe/version-checker"><img src="https://agentmods.dev/badge/agents/vericontext/vibeframe/version-checker/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/vericontext/vibeframe/version-checker"><img src="https://agentmods.dev/badge/agents/vericontext/vibeframe/version-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 891 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.

Model	Per session	Once invoked
Fable 5.1	$0.00032	$0.00891
Opus 5.5	$0.00013	$0.00356
Sonnet 5.5	$0.00006	$0.00178
Haiku 4.5	$0.00003	$0.00089

Measured 13d ago against content hash d4e8676611dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

version-checker 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 13d 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.

.claude/agents/version-checker.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a version and info sync checker for VibeFrame, a CLI/MCP monorepo for frontier AI video generation for coding agents.

What to Check

Run all checks and report discrepancies.

1. Version Sync

All package.json files must have the same version:

package.json (root)
packages/cli/package.json
packages/core/package.json
packages/ai-providers/package.json
packages/mcp-server/package.json
apps/web/package.json

Also check apps/web/app/page.tsx and README.md for any hardcoded version strings.

2. Test Count

README.md: badge and body text (e.g., "264 passing")
apps/web/app/page.tsx: feature card text (e.g., "264 tests")
Actual count: run pnpm -F @vibeframe/cli exec vitest run 2>&1 | tail -5 and extract the number

3. Tool & Provider Counts

CLI command count: pnpm vibe schema --list
Provider/tool counts: bash scripts/sync-counts.sh --check
Compare against:
- apps/web/app/page.tsx: hero counts and command claims
- README.md: provider/command claims
- CLAUDE.md: developer guidance

4. Install URL

Must be consistent across:

README.md: install commands
apps/web/app/page.tsx: install command
scripts/install.sh: the actual script

Canonical URL: https://vibeframe.ai/install.sh

5. MCP Config

MCP server package name and config JSON should match across:

README.md
CLAUDE.md
packages/mcp-server/README.md

6. CLI Command Sync

Generated CLI docs must match the built CLI.

How to check:

Run pnpm build
Run pnpm gen:reference:check
Run pnpm vibe schema --list and confirm the top-level groups align with README: generate, edit, inspect, audio, remix, init, build, render, run, scene, timeline, detect, batch, media, guide, context, completion.
Confirm README.md and docs/ use current commands, not removed namespaces such as vibe ai, vibe project, vibe export, or vibe pipeline.

Report:

CLI reference status
Public docs with removed/stale commands
Count: docs cover the intended top-level groups or explain why not

Read the full file on GitHub · 128 lines

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.

13d ago Changed d4e8676611dc
21d ago Changed · -1 lines 5a341ae0b1df
2mo ago First seen · 129 lines · 32 tokens per session scan A 5016c3d585c7

Subscribe to this mod's changes

version-checker is an agent published in the GitHub repository vericontext/vibeframe (185 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 891 once invoked, about $0.0001 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-30.

Git and workflow Releases ai ai-agents claude cli developer-tools ffmpeg

version-checker next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
version-checkervericontext/vibeframe	Agent	185	yesterday	MIT	A	32	Claude Code
git-workflowFortiumPartners/ensemble	Agent	12	yesterday	MIT	A	29	Claude Code
git-masterLucasSantana-Dev/sharekit	Agent	2	4d ago	MIT	A	18	Claude Code
release-managerfatihkan/badi	Agent	7	1mo ago	MIT	A	24	Claude Code
bobby-shipccevans/bobbycode	Agent	6	5d ago	MIT	A	32	Claude Code
pr-ghostwriterfatihkan/badi	Agent	7	1mo ago	MIT	A	16	Claude Code
archiveresneiderbravo/speclaw	Agent	3	18d ago	MIT	A	25	Claude Code

vibeframe: Agent for Claude Code