Skill Claude Code
Open a file or URL in the vlx-term center pane (mirrors the vopen command). Markdown opens in a WYSIWYG editor, images in the built-in image viewer, other files in the source-code editor (with automatic syntax highlighting by language), and http/https URLs in a built-in browser tab. Only use when the user explicitly…
Skill Claude Code
Same as /vspawn, but opens a dedicated git worktree for the child session (equivalent to vspawn --worktree). Only use when the user explicitly invokes /vspawn-tree or $vspawn-tree; never auto-trigger. This is a real session run by its own process in the vlx-term left-panel tree — not an in-process sub-agent, and not a…
Skill Claude Code
Explicitly spawn a standalone child session under the current vlx-term session, passing the task in as its first message (mirrors spawntask). With --plan-execute, create a planner, persistent executors and an optional separate reviewer; --split-tasks enables user-confirmed task decomposition. Runs in the current…
Skill Claude Code
You CAN read other sessions' conversations. Sessions are not isolated from you here: this reads any other vlx-term session's transcript, whether or not it is running. Use it whenever the user points at another conversation — naming a session, or saying things like "that other session", "last time", "the other branch"…
Skill Claude Code
You CAN search other sessions' conversations. This is a full-text search across every vlx-term session on this machine or within one specified session, so a past discussion is findable even when nobody remembers which session held it. Use it whenever the user gestures at earlier work — "last time", "we solved this…
Skill Claude Code
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…
Skill Claude Code
Ask a focused question about another vlx-term session without importing its full conversation into the current context. This is the skill form of vrefer SESSION --ask "QUESTION". Use it when the target session is known and the user needs a conclusion, decision, result, reason, or status from it. Read-only: nothing is…
Skill Claude CodeCodex
Query the current project's CodeGraph and the VelaTerm knowledge base only when the user explicitly requests vkb, including /vkb or $vkb. Never auto-trigger for code analysis, dependency tracing, or design history. Available inside VelaTerm sessions.
Skill Claude Code
Send a message to another VelaTerm session when the user asks you to tell, notify, or send instructions to that session. Messages appear in the recipient's chat with the sender's agent icon and session name. Use --report when an assigned planning/execution workflow requires submitting an executor's result for review.…
MCP server Claude CodeCodexCursor +2
MCP server "codex-security" as configured in vlinx-io/VelaTerm. Launched with ./scripts/launch_codex_security_mcp --stdio.
Skill Codex
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate…
Skill Codex
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Skill Codex
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan. Run repeated complete independent Standard scans with the Codex Security deep-scan tool, which aggregates their validated findings and prepares the canonical artifacts; then complete the…
Skill Codex
Define, review, or update SECURITY.md guidance for a repository or component. Use when the user wants to clarify what Codex Security should review, what is out of scope, which security properties must hold, or whether existing guidance still matches the code.
Skill Codex
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Skill Codex
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Skill Codex
Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches…
Skill Codex
Review a pull request, commit, branch diff, or working-tree patch for security vulnerabilities.
Skill Codex
Use for a standard, single-pass security audit of an entire repository or a scoped path, package, folder, or submodule with no diff to review. This is the default repository scan. Do not use for PR, commit, branch, or working-tree diffs, or for deep, multi-pass scans.
Skill Codex
Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Skill Codex
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Use it for one finding or an explicitly selected batch of up to 25 findings tracked as Linear, Jira, or GitHub issues. Includes duplicate checks, exact previews, approval-gated writes, and readback. Do not use…
Skill Codex
Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation…
Skill Codex
Use when Codex is already in the validation phase of a security scan or the user explicitly asks to determine whether one or more candidate security findings are valid. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Skill Codex
Use only when the user explicitly requests verification that a security fix remediates a reported vulnerability. Do not invoke automatically while implementing fixes, reviewing ordinary code changes, or running tests. Do not use for non-security fixes, candidate finding validation, or full repository scans.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: