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 agentmods add skills/vlinx-io/velaterm/vspawnnpx skills add vlinx-io/VelaTerm --skill vspawngit clone --depth 1 https://github.com/vlinx-io/VelaTermWrote 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/vlinx-io/velaterm/vspawn)<a href="https://agentmods.dev/skills/vlinx-io/velaterm/vspawn"><img src="https://agentmods.dev/badge/skills/vlinx-io/velaterm/vspawn.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 | $0.00118 | $0.00972 |
| Opus 5 | $0.00059 | $0.00486 |
| Sonnet 5 | $0.00024 | $0.00194 |
| Haiku 4.5 | $0.00012 | $0.00097 |
Grade A, and why
vspawn 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 5d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vspawn
The user explicitly invoked /vspawn (Claude) or $vspawn (Codex) to request spawning a standalone child
session under the current vlx-term session,
passing the task in as its first message. The new child session runs as a brand-new claude/codex process, and
by default runs in the current directory without a worktree (to open a dedicated git worktree for the child
task, use /vspawn-tree, or add --worktree to this command).
⚠️ This is not an in-process sub-agent, and not a background Task: it is a real, visible, interactive, resumable session tab in the vlx-term left-panel tree, run by its own process, leaving the current session undisturbed.
User input:
$ARGUMENTS
Step 1: Expand the user input into a "self-contained" rich prompt (critical)
The new child session is a brand-new conversation with no memory of this one. Do not forward the user's one-liner verbatim — as if handing the job to someone with zero context, use what is known from the current conversation to expand it into a task description that stands on its own. Write whichever of the following apply — don't pad:
- Goal: what needs to be achieved.
- Relevant files and paths: spell them out (absolute or relative), don't make them guess.
- Established facts / conclusions: key information from this conversation that they wouldn't know (e.g. an already-located root cause, an already-agreed convention).
- Constraints: tech stack, things that must not change, code-style requirements.
- Acceptance criteria: what counts as done.
Don't write "see above / as mentioned / continuing from earlier" — the new session can't see any of this. (If the user's input is already complete, or they explicitly say "keep it short," don't over-expand.)
Step 2: Detect worktree / type options
Detect the following intents from the user input; when detected, turn them into the corresponding command flag, and do not write that instruction into the prompt:
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.
- 5d ago First seen · 76 lines · 118 tokens per session scan A 2c407cb2a12c
vspawn is a skill published in the GitHub repository vlinx-io/VelaTerm (111 stars, last pushed 9d ago), licensed MIT. It adds 118 tokens to every session and 972 once invoked, about $0.0006 per session on Opus 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.
Other skills, from other repositories
linear-tickets
Use Orca's Linear CLI through orca linear ... commands to read linked ticket context with orca linear issue --current --full --json, post completion updates, move work forward through Linear workflow states, attach PR/MR links with orca linear attach --current --url --title "PR/MR link" --json, and triage Linear tasks…
computer-use
Use Orca's computer-use CLI for OS/window-level inspection and input in visible local app windows. Use when a task must read or operate a native app or an external browser window (for example, Chrome, Edge, or Safari) or an app webview. Do not use for Orca's embedded browser or page-only browser automation. Use…
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
create-skill
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
harbor
Run Terminal-Bench or any Harbor dataset with Ante as the agent, using the Harbor adapter in the ante repo's ante-harbor/ directory. Use when the user wants to benchmark Ante on Harbor or reproduce Ante's published eval results.
logging-and-error-reporting
How and when to log (log:: levels, safe macros) and report errors to Sentry (reporterror!) in the Warp codebase. Use when adding or reviewing any logging or error reporting — picking a log level, deciding log vs. reporterror!, keeping sensitive data out of logs, or surfacing an error to Sentry.