Borrowing it
Nothing to install: this file belongs to opencue/cuecards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opencue/cuecards/main/.agents/skills/vc-update/SKILL.mdgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/vc-update)<a href="https://agentmods.dev/skills/opencue/cuecards/vc-update"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/vc-update.svg" alt="Measured on agentmods" 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.00029 | $0.02107 |
| Opus 5 | $0.00015 | $0.01053 |
| Sonnet 5 | $0.00006 | $0.00421 |
| Haiku 4.5 | $0.00003 | $0.00211 |
Grade C, and why
vc:update 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 3d 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.
- If a real directory exists at the path: `rm -rf` it first. How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vc-update
Pull the latest agent harness improvements from the remote vibecode-pro-max-kit repository into the current project.
When to Use
- After being told a new harness version is available
- Periodically to check for updates
- After bootstrapping a project with
vc-setupand wanting the latest improvements
Workflow
Follow these steps exactly. Do NOT skip the dry-run or confirmation step.
Step 1: Check Worktree Status
Run git status --porcelain in the project root.
- If output is non-empty: warn the user that they have uncommitted changes and suggest
git stashor committing first. Do not block -- continue after warning. - If output is empty: proceed silently.
Step 2: Read Current Version
Read the file .vc-version in the project root.
- If it exists: store its contents as
currentVersion(a semver string like2.0.4). - If it does not exist: set
currentVersionto"0.0.0"(treat as first update).
Step 3: Clone Remote Repository
TMPDIR="/tmp/vc-update-$(date +%s)"
git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git "$TMPDIR"
If the clone fails (network error, auth error, repo not found):
- Print the error message.
- Clean up the temp directory if it was partially created.
- Stop. Do not proceed.
Step 4: Resolve Remote Manifest
Run the resolver script from the cloned repo:
node "$TMPDIR/resolve-manifest.mjs" --root "$TMPDIR" --json
Parse the JSON output to extract:
files(string[]) -- resolved managed file pathsmerge(string[]) -- files where user customizations are preserved (not overwritten)copyIfMissing(string[]) -- files only installed if they don't already exist locallystrip(string[]) -- files needing content stripping (informational)symlinks(object) -- symlink path -> target mappings
Extract the remote version from the manifest:
node -e "console.log(JSON.parse(require('fs').readFileSync('$TMPDIR/vc-manifest.json','utf8')).version)"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 204 lines · 29 tokens per session scan C e169500c3da3
vc:update is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 2,107 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…