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 opencue/cuecards --skill vc-watzupgit 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-watzup)<a href="https://agentmods.dev/skills/opencue/cuecards/vc-watzup"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/vc-watzup/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/opencue/cuecards/vc-watzup"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/vc-watzup.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.00042 | $0.00847 |
| Opus 5.5 | $0.00017 | $0.00339 |
| Sonnet 5.5 | $0.00008 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
vc:watzup 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watzup
Summarize the current Flowser repo state for handoff and resume work.
This is a helper skill only.
- Do use it for read-only branch, worktree, and active-plan summaries.
- Do use it to surface likely selected-plan context when it can be proven or safely hinted.
- Do not use it to choose a plan authoritatively.
- Do not use it to approve execution, resume execution, or mutate repo/process state.
Core Contract
watzup is advisory.
- Evidence comes from git, worktree metadata, and
process/*plan inventory. - Selected-plan awareness is a hint, not a command.
- Next-step recommendations are suggestions, not workflow gates.
If a user needs execution, the repo still requires explicit plan selection and ENTER EXECUTE MODE.
Invocation
Run the local scanner:
node .Codex/skills/watzup/scripts/watzup-scan.cjs --json
Useful flags:
node .Codex/skills/watzup/scripts/watzup-scan.cjs
node .Codex/skills/watzup/scripts/watzup-scan.cjs --json --max-branches 8 --plan-limit 6
node .Codex/skills/watzup/scripts/watzup-scan.cjs --selected-plan process/general-plans/active/example_PLAN_27-05-26.md
node .Codex/skills/watzup/scripts/watzup-scan.cjs --since "14 days ago"
node .Codex/skills/watzup/scripts/watzup-scan.cjs --fetch
Input Sources
The scanner reads from:
git status --short --branchgit worktree list --porcelain- local and remote branch refs plus sampled recent commits
process/general-plans/active/process/features/*/active/- optional session-state hints if a local session id is present
It does not scan upstream plans/**, and it never treats a selected-plan hint as execute authority.
Output Shape
The default output is a human-readable report with these sections:
- Current State
- Recent Work
- In-Flight Plans
- Next Steps
- Warnings
--json returns the same information as structured data.
If the scanner fails, say that explicitly and fall back to the minimal read-only commands:
git status --short --branch
git worktree list --porcelain
git for-each-ref --format='%(refname:short) %(committerdate:iso8601) %(objectname:short) %(subject)' refs/heads refs/remotes
find process/general-plans/active process/features -path '*/active/*' -type f | sort
What ships with it
3 files 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.
- 1mo ago First seen · 101 lines · 42 tokens per session scan A 70949a115e60
vc:watzup is a skill published in the GitHub repository opencue/cuecards (6 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 847 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
parallel-work-check
Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
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…
{{BUCKET}}-management
Skill "{{BUCKET}}-management" from damusix/atomic-claude, covering purpose, doc shape and frontmatter contract.