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.
git clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/commands/notque/vexjoy-agent/install)<a href="https://agentmods.dev/commands/notque/vexjoy-agent/install"><img src="https://agentmods.dev/badge/commands/notque/vexjoy-agent/install/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/commands/notque/vexjoy-agent/install"><img src="https://agentmods.dev/badge/commands/notque/vexjoy-agent/install.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00016 | $0.00580 |
| Opus 5.5 | $0.00006 | $0.00232 |
| Sonnet 5.5 | $0.00003 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
install 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.
What it actually says
Install or repair VexJoy Agent with the vexinstall engine. The engine lives in scripts/vexinstall/; its layout contract is in docs/installer-layout.md.
-
Show the plan. It writes nothing:
PYTHONPATH=<repo>/scripts python3 -m vexinstall plan --target allReport the per-target counts (add, replace, remove, adopt, blocked, collisions) and any
CAP-TRIPPEDornote:lines. Exit 3 means a name collision: name both sources and stop. -
Ask the user before applying. Apply only the targets the user approves:
PYTHONPATH=<repo>/scripts python3 -m vexinstall apply --target <target>Never pass
--allow-mass-remove,--adopt-source, or--modeunless the user asks for that flag by name after reading the plan. -
Check the result:
PYTHONPATH=<repo>/scripts python3 -m vexinstall doctor --target <target>
Exit codes: 0 ok, 1 error, 2 usage, 3 collision, 4 guard (write into the repo refused), 5 mass-removal cap, 6 source refused (worktree, /tmp, or moved repo), 7 lock timeout.
./install.sh runs apply --takeover for every present runtime; the SessionStart hook runs sync --target all. Pass --takeover to apply only when the plan shows takeover entries the user wants replaced. Undo an apply with python3 -m vexinstall restore-trash <ts> and restore-settings <ts>.
Profiles and updates
apply and sync also link each CLAUDE_CONFIG_DIR profile in ~/.claude-accounts/accounts.json to ~/.claude and register the toolkit hooks in the profile's settings.json, keeping its other keys. doctor prints account-hooks-drift with missing= and stale= counts when a profile is behind.
Run the installer from a clean main clone, not a working branch, so live hooks track main. After a merge, update every profile with one command:
git -C <clean-clone> pull --ff-only && <clean-clone>/install.sh
The SessionStart sync runs only when the session starts in a toolkit checkout, so it does not keep profiles current for sessions in other repos. It never pulls.
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.
- today Changed · +12 lines 13b636ffb35e
- 24d ago Changed · +26 lines · +5 tokens per session 0a8b27209bc7
- 1mo ago First seen · 7 lines · 11 tokens per session scan A 0539dbc0ee90
install is a command published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 580 once invoked, about $0.0001 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 commands, from other repositories
ui5-version
Display UI5 version information, support status, release notes, and upgrade paths.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
plan-localization
Plan localisation covering extraction, translation workflow, and the layout and format issues that follow.
persuasion
/volumes/vixinssd/wizardsoftheghosts/generated/openclaw/persuasion/SKILL.md.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.