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 vlinx-io/VelaTerm --skill vspawn-treegit 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-tree)<a href="https://agentmods.dev/skills/vlinx-io/velaterm/vspawn-tree"><img src="https://agentmods.dev/badge/skills/vlinx-io/velaterm/vspawn-tree/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/vlinx-io/velaterm/vspawn-tree"><img src="https://agentmods.dev/badge/skills/vlinx-io/velaterm/vspawn-tree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00096 | $0.01815 |
| Opus 5.5 | $0.00038 | $0.00726 |
| Sonnet 5.5 | $0.00019 | $0.00363 |
| Haiku 4.5 | $0.00010 | $0.00181 |
Grade A, and why
vspawn-tree 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 6d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vspawn-tree
The user explicitly invoked /vspawn-tree (Claude) or $vspawn-tree (Codex) to request spawning a standalone
child session under the current vlx-term session,
passing the task in as its first message. The only difference from /vspawn: it opens a dedicated git worktree
for the child session (a separate workspace/branch), suited to cases where you don't want to pollute the current
workspace and want the child task to run on an isolated branch.
⚠️ 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
Planning and execution mode
When the user requests planning and execution, add --plan-execute. Keep this conversation as the
initiator; a new planner organizes work and dispatches to persistent execution sessions. Independent review is disabled by default; add --review when the user requests review, which then runs in a separate Review session. Plan only collects context, coordinates and summarizes in either mode.
Add --split-tasks when the user requests task decomposition. Do not plan, split or implement the task
in this conversation, and do not use in-process subagents.
For a skill invocation with both flags, automatically add --yes unless the user explicitly requests
the initial configuration dialog. The planner starts without a launch dialog, but its proposed tasks
still require the user's final review before any executor starts. Never confirm tasks for the user.
Without splitting, retain the ordinary confirmation behavior.
Pass only explicit role selections through --plan-agent, --plan-model, --plan-effort, --exec-agent,
--exec-model and --exec-effort. The backend resolves omitted values from the initiating session and
supported defaults. Only backend chat-capable agents can run the workflow. The final review can edit
each executor's settings, but cannot change the already-started planner's settings or directory mode.
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.
- 6d ago Changed · +2 lines ebe87c227246
- 13d ago Changed 70766b37d29f
- 14d ago Changed d333773db00d
- 1mo ago Changed · +33 lines ef86b2b38c13
- 1mo ago Changed · +9 lines 2bd85e8a8345
- 1mo ago First seen · 71 lines · 96 tokens per session scan A eb515f37afb1
vspawn-tree is a skill published in the GitHub repository vlinx-io/VelaTerm (308 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 1,815 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
factory-deferred-repositories
Use when a Factory task's frozen deferred repository inventory lists a repository needed for the task that is not already checked out. Verify current access and an unused target before checking it out on demand; never overwrite an existing checkout or expose credentials.
oz-report-pr
Report a pull request back to the Oz platform after creating one.
critty
Review code changes or a document with Critty's terminal UI and address the reviewer's inline comments round by round. Use when the user or an approval workflow selects Critty; a generic review request does not count.
contribute
Set up a Superset open-source contribution, from forking and cloning superset-sh/superset through local dev setup and the repo's rules to a merge-ready PR. Use when the user wants to contribute to Superset, fix a Superset bug themselves, add a feature to Superset, or prepare a PR against superset-sh/superset.
macos-release
Release a native macOS app to GitHub with DMG packaging and Sparkle appcast updates. Use this skill whenever the user wants to publish a new version, create a release, ship an update, push a release to GitHub, or update the appcast. Also trigger when the user mentions DMG creation, Sparkle signing, notarization…
review-pr
Review and merge GitHub pull requests for Spatie packages. Use when asked to review a PR, review a pull request, merge a PR, or when given a GitHub PR URL to review. Also triggers on 'review this PR,' 'check this pull request,' 'merge this,' or '/review-pr'. Uses gh CLI for all GitHub operations.