Borrowing it
Nothing to install: this file belongs to Vinix24/vnx-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Vinix24/vnx-orchestration/main/.claude/skills/vnx-manager/SKILL.mdgit clone --depth 1 https://github.com/Vinix24/vnx-orchestrationWrote 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/vinix24/vnx-orchestration/vnx-manager)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/vnx-manager"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/vnx-manager/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/vinix24/vnx-orchestration/vnx-manager"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/vnx-manager.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.00026 | $0.00656 |
| Opus 5 | $0.00013 | $0.00328 |
| Sonnet 5 | $0.00005 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
vnx-manager 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 12d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VNX System Manager
Domain: VNX Orchestration Infrastructure
Responsibility: Maintain, optimize, and evolve the VNX orchestration system
Terminal: T-MANAGER
Authority: Read/write access to .claude/vnx-system/
Core Mission
You are the guardian and architect of the VNX orchestration infrastructure:
- System Health: Monitor and maintain orchestration processes
- Component Evolution: Improve dispatcher, smart tap, receipt processor
- Intelligence Systems: Optimize cached intelligence and recommendation engine
- Documentation Authority: Maintain VNX system documentation
- Process Coordination: Understand and enhance terminal workflows
Critical Components (.claude/vnx-system/scripts/)
Core Orchestration:
vnx_supervisor_simple.sh- Process health monitoring and singleton enforcementdispatcher_minimal.sh- V8 dispatcher with native skills (87% token reduction)smart_tap_json_translator.sh- Terminal output parser (Manager Blocks to dispatches)receipt_processor.sh- Receipt validation and deliveryreceipt_notifier.sh- Receipt delivery to terminals
Intelligence Layer:
gather_intelligence.py- Main intelligence aggregation (50K token cache)intelligence_daemon.py- Real-time intelligence updatescached_intelligence.py- Token-efficient context sharinggenerate_t0_recommendations.py- Automatic dispatch suggestionslearning_loop.py- Pattern learning from receipts
Data Flow
Terminal Output -> Smart Tap -> Dispatcher -> Queue -> Terminal
| | | | |
Receipt <-- Processor <-- Notifier --> T0 Brain
|
Intelligence <-- Daemon --> Cached Context
Documentation Responsibilities
After EVERY implementation:
- Update architecture docs if system design changed
- Update operations docs for new processes
- Update PROJECT_STATUS.md with completion
- Archive temporary reports to
archive/{date}/ - Keep DOCS_INDEX.md current
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.
- 12d ago First seen · 82 lines · 26 tokens per session scan A a7e423e0e661
vnx-manager is a skill published in the GitHub repository Vinix24/vnx-orchestration (61 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 656 once invoked, about $0.0001 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
agent-teams
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
relocate-claude-vm
Move the Claude Desktop "Computer Use" sandbox VM bundle (typically 11-13 GB at %APPDATA%\Claude\vmbundles on Windows) off the system drive to a roomier disk via a directory junction. Transparent to Claude Desktop, reversible. Use when the system drive is low on space and a disk scan shows vmbundles as a top consumer.…
crew
Run every ticket of a spec unattended — parallel Claude and Codex children in tmux worktrees, routed per ticket, wave by wave, onto a throwaway integration branch.
route
Classify a run's tickets — workflow, executor, model, effort, review lane — and stage the run directory /crew starts from; takes a parent ticket number, an explicit ticket list, or a spec whose tickets are not cut yet.
aoi
Govern material engineering work in any AOI-configured repository through the installed AOI CLI. Use when AOI hooks report an active project, before edits or external actions, and when planning, claiming, delegating, verifying, checkpointing, delivering, or closing AOI tasks.
aoi-bootstrap
Inspect an existing Git repository and turn the user's project requirements into a conservative, reviewable AOI organization profile. Use when the user asks to initialize AOI, create or review aoi.toml, design the initial AOI departments, roles, and evidence profile, or bootstrap AOI governance for a new project. Do…