vs-queue

vs-queue is a command for Claude Code from mtarcure/claude-vibe-squad. It costs 0 tokens per session (264 once invoked), scanned A, original, MIT.

A command that shows tasks waiting for the operator followed by live or in-progress squad tasks. It reads the current task summary without rewriting the saved session-resume file.

In plain words
What is it for?
Use it to see what needs your decision and what dispatched, running, or review-required tasks remain.
Why use it?
It puts requests for your input and unfinished work in one view, so you do not have to inspect several status files.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to see what needs your decision and what dispatched, running, or review-required tasks remain.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/mtarcure/claude-vibe-squad/vs-queue
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.

Clone the repo
git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad

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.

agentmods badge for vs-queue

README.md
[![agentmods](https://agentmods.dev/badge/commands/mtarcure/claude-vibe-squad/vs-queue/github.svg)](https://agentmods.dev/commands/mtarcure/claude-vibe-squad/vs-queue)
Your own site
<a href="https://agentmods.dev/commands/mtarcure/claude-vibe-squad/vs-queue"><img src="https://agentmods.dev/badge/commands/mtarcure/claude-vibe-squad/vs-queue/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 vs-queue

Your own site · 80×15
<a href="https://agentmods.dev/commands/mtarcure/claude-vibe-squad/vs-queue"><img src="https://agentmods.dev/badge/commands/mtarcure/claude-vibe-squad/vs-queue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 264 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.00000 $0.00264
Opus 5.5 $0.00000 $0.00106
Sonnet 5.5 $0.00000 $0.00053
Haiku 4.5 $0.00000 $0.00026

Measured today against content hash 5b8d36e32963, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vs-queue 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 today.

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/commands/vs-queue.md · 29 lines

What it actually says

/vs-queue

Show what is waiting on the operator, then the live / in-flight board tasks.

Run:

root="$(git rev-parse --show-toplevel)"
awaiting="$root/_state/chrono/awaiting-operator.md"
if [ -f "$awaiting" ]; then
  echo "== Awaiting operator =="
  cat "$awaiting"
  echo
fi
echo "== Live tasks (dispatched / in-flight / review-required) =="
bash "$root"/bin/chrono-resume-capsule.sh --stdout \
  | awk '/^## Live tasks/{p=1;print;next} p&&/^## /{exit} p'

--stdout regenerates the capsule fresh and prints it without rewriting _state/chrono/resume.md (that file is Chrono's session-resume contract to manage, so this viewer leaves it alone).

Note: the capsule has no section literally named "Pending completions"; the section that lists work awaiting completion is ## Live tasks (dispatched / in-flight / review-required), which is what this extracts.

Use this when the operator says /vs-queue, "what's pending", or asks what needs their input or is still running.

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. today First seen · 29 lines · 0 tokens per session scan A 5b8d36e32963

Subscribe to this mod's changes

vs-queue is a command published in the GitHub repository mtarcure/claude-vibe-squad (178 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 264 tokens. 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-10-29.