New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vstat

by vlinx-io in vlinx-io/VelaTerm

You CAN see whether other vlx-term sessions are busy. An agent skill from vlinx-io/VelaTerm.

MITAuto-check passed

Install Vstat

skills CLI
$ npx skills add vlinx-io/VelaTerm --skill vstat -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vlinx-io/VelaTerm vstat --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vlinx-io/VelaTerm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vstat .claude/skills/vstat && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vstat
GitHub stars
270
Token cost
~825 tokens
SKILL.md length
339 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

You CAN see whether other vlx-term sessions are busy. An agent skill from vlinx-io/VelaTerm.

  • The user asks how a run
  • SKILL.md covers Forms, When to use which, Reading the result and Notes
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Another session is doing (is it done yet

What it does

Vstat is an agent skill from vlinx-io/VelaTerm. You CAN see whether other vlx-term sessions are busy. This reports each session's current state — working, asking for permission, waiting for input — straight from the same status the sidebar shows. Use it when the user asks how a run or another session is doing ("is it done yet", "what are they up to", "how is the orchestration going") in any language, or when checking execution-session activity. Read-only and instant; nothing is sent to any session. Available only inside vlx-term-hosted sessions.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: VelaTerm = Codex + iTerm2, The Best ADE for AI Coding. The licence is MIT.

When your agent uses it

  • The user asks how a run
  • Another session is doing (is it done yet
  • What are they up to
  • How is the orchestration going) in any language

Example prompts

  • “is it done yet”
  • “what are they up to”
  • “how is the orchestration going”
  • “/vstat”

Requirements

  • Pre-approved tools (allowed-tools): Bash(vstat:*)

What it can do on your machine

Read from SKILL.md and the folder at commit 98b5f2f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(vstat:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vstat loads about 825 tokens when it runs. Until then it costs about 127 tokens; SKILL.md has 339 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~127
When it runs · the whole SKILL.md, loaded when a task matches
~825

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vlinx-io/VelaTerm at commit 98b5f2f, republished under its MIT licence (© vlinx-io). 339 words, ~825 tokens.

Download SKILL.mdSave it as .claude/skills/vstat/SKILL.md (or your agent's skills folder).
name
vstat
description
You CAN see whether other vlx-term sessions are busy. This reports each session's current state — working, asking for permission, waiting for input — straight from the same status the sidebar shows. Use it when the user asks how a run or another session is doing ("is it done yet", "what are they up to", "how is the orchestration going") in any language, or when checking execution-session activity. Read-only and instant; nothing is sent to any session. Available only inside vlx-term-hosted sessions.
allowed-tools
Bash(vstat:*)
argument-hint
[<orch-id>|latest] [--wait] [--follow] [--timeout N] [--json]

vstat

vstat prints which vlx-term sessions are working, asking, waiting, or running background work. The answer comes from the same authoritative status the sidebar displays, not from reading screens.

For planning/execution task progress, use vflow list [session] to find workflow and execute IDs, then vflow status <workflow-id> from a workflow member session for task states, independent rounds and delivery receipts. For ordinary session hierarchy and saved properties, use vself [session] --json. vstat reports activity only; idle does not establish acceptance.

Forms

bash
vstat                     # every session known to vlx-term
vstat latest              # the most recent legacy orchestration from this session
vstat <orch-id>           # one specific run
vstat latest --wait       # block until something in that run changes, then print
vstat latest --follow     # keep printing changes until every agent has stopped
vstat --json              # machine-readable output, with any of the above

Each line is <id prefix> <state> <kind> <name> <how long in that state>. A state of unknown means the session has not reported yet, which usually means it is still starting.

When to use which

  • Plain vstat or vstat latest answers "how is it going" right now. Use this from a conversation.
  • --wait is for scripts that want the next change without polling. It returns after one change or after --timeout seconds (default 60, at most 300).
  • --follow remains available to historical orchestration coordinator tabs. Do not run it from a conversation: it holds the turn until every agent has stopped.

Reading the result

  • working: the agent is in the middle of a turn.
  • asking: it is blocked on a permission prompt and needs a person.
  • waiting: it has stopped and is waiting for input. For a child session that was given one task, this means the task is finished, or the agent gave up; read its conversation with vrefer to tell which.
  • background: its turn has ended, but work that turn started (a background task or a vrun command) is still running. The agent usually resumes on its own when that work finishes, so the task is not done.

Notes

  • Must run inside a vlx-term-hosted session: it relies on the injected VLX_* environment variables and vstat on PATH; if missing it reports "not inside a VelaTerm session" and exits.
  • latest and orchestration IDs refer to historical runs from the retired vorch command. New task-splitting workflows use vflow status; the unfiltered vstat listing still includes their active sessions.

© vlinx-io, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/vstat of vlinx-io/VelaTerm.

Open the folder on GitHubat commit 98b5f2f

Compare with similar skills

Vstat next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vstat compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vstat this skillvlinx-io/VelaTerm270—~825Automated safety check: PassMIT
Session Handoffsickn33/agentic-awesome-skills47k—~1.8kAutomated safety check: NotesMIT
Sessionanthropics/claude-for-legal9.6k3 repos~478Automated safety check: PassApache-2.0
Session History Searchslopus/happy24k—~3.1kAutomated safety check: PassMIT
Session Handoffdavila7/claude-code-templates32k2 repos~1.6kAutomated safety check: PassMIT
Read Sessionasgeirtj/system_prompts_leaks69k—~2.4kAutomated safety check: PassCC0-1.0

Similar skills

  • Session Handoff

    sickn33/agentic-awesome-skills

    A skill your agent uses when context approaches capacity, before /clear or /compact, when switching tasks, or when ending a coding session: produces a structured handoff artifact for the next session.

    47k GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

  • Session

    anthropics/claude-for-legal

    Official

    Run a focused N-question study session on a subject — MBE, essay, or flashcards.

    9.6k GitHub starsUsed in 3 repos~478 tokens
    EducationAuto-check passed

  • Session History Search

    slopus/happy

    Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Session Handoff

    davila7/claude-code-templates

    Creates comprehensive handoff documents for seamless AI agent session transfers.

    32k GitHub starsUsed in 2 repos~1.6k tokens
    Agent WorkflowsAuto-check passed

  • Read Session

    asgeirtj/system_prompts_leaks

    Locate and read Muse Code's OWN session logs — the current session or a prior one.

    69k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Coding Agent Session Finder

    code-yeongyu/oh-my-openagent

    Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.

    70k GitHub starsUsed in 1 repo~2.8k tokens
    Agent WorkflowsAuto-check passed

More from vlinx-io/VelaTerm

All 26 skills in this repo

  • Assess Patch Risk

    vlinx-io/VelaTerm

    Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility.

    270 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Vspawn

    vlinx-io/VelaTerm

    Explicitly spawn a standalone child session under the current vlx-term session, passing the task in as its first message (mirrors spawntask).

    270 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

  • Deep Security Scan

    vlinx-io/VelaTerm

    A skill your agent uses when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan.

    270 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

  • Define Security Policy

    vlinx-io/VelaTerm

    Define, review, or update SECURITY.md guidance for a repository or component.

    270 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Track Findings

    vlinx-io/VelaTerm

    Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories.

    270 GitHub stars~5.1k tokensUpdated yesterday
    Auto-check passed

  • Verify Fix

    vlinx-io/VelaTerm

    Use only when the user explicitly requests verification that a security fix remediates a reported vulnerability.

    270 GitHub stars~757 tokensUpdated yesterday
    Auto-check passed

Questions about Vstat

What does Vstat do?

You CAN see whether other vlx-term sessions are busy. An agent skill from vlinx-io/VelaTerm. Vstat is an agent skill from vlinx-io/VelaTerm. You CAN see whether other vlx-term sessions are busy.

When should I use Vstat?

Vstat fits situations like: the user asks how a run; another session is doing (is it done yet; what are they up to; how is the orchestration going) in any language.

How do I install Vstat in Claude Code?

Run `npx skills add vlinx-io/VelaTerm --skill vstat -a claude-code`. Or copy the skill folder (skills/vstat in vlinx-io/VelaTerm) into .claude/skills/vstat in your project. Claude Code loads it when a task matches its description.

How do I install Vstat in Codex?

Run `npx skills add vlinx-io/VelaTerm --skill vstat -a codex`. Or copy the skill folder (skills/vstat in vlinx-io/VelaTerm) into .agents/skills/vstat in your project. Codex loads it when a task matches its description.

Can I use Vstat in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vlinx-io/VelaTerm --skill vstat -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vstat, .gemini/skills/vstat, .github/skills/vstat and .opencode/skills/vstat in your project.

What does Vstat need to run?

SKILL.md names no scripts, command-line tools or credentials: Vstat is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(vstat:*).

Does Vstat access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vstat safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vstat use?

Vstat is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vstat use?

About 825 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vstat?

Skills that share tags, products or a category with Vstat: Session Handoff (sickn33/agentic-awesome-skills, 47k stars), Session (anthropics/claude-for-legal, 9.6k stars), Session History Search (slopus/happy, 24k stars) and Session Handoff (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vstat?

vlinx-io (a GitHub user) maintains it in vlinx-io/VelaTerm, which has 270 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.

Source: vlinx-io/VelaTerm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.