vnx-orchestration: Skill for Claude Code

.claude/skills/control-centre/SKILL.md

control-centre is a skill for Claude Code from Vinix24/vnx-orchestration. It costs 35 tokens per session (1,013 once invoked), scanned A, original, MIT.

A supervisor guide for coordinating several VNX project coordinators from one interactive session. It monitors their status, forwards tasks to individual projects, and combines information across projects without changing application code.

In plain words
What is it for?
Use it to inspect project and coordinator health, view heartbeats and event counts, send a task to a selected project, and aggregate status across projects. It is for read-only coordination and monitoring.
Why use it?
It provides one place to see which projects are running, stalled, terminating, or finished. It also prevents the supervisor from bypassing the per-project coordinators or making direct code changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

This is Vinix24/vnx-orchestration's own configuration. It tells Claude Code how to work on vnx-orchestration itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vnx-orchestration configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/control_centre_cli.py status.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Vinix24/vnx-orchestration/main/.claude/skills/control-centre/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Vinix24/vnx-orchestration

Made for: Claude Code.

Wrote 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.

agentmods badge for control-centre

README.md
[![agentmods](https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/control-centre/github.svg)](https://agentmods.dev/skills/vinix24/vnx-orchestration/control-centre)
Your own site
<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/control-centre"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/control-centre/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.

agentmods 80×15 button for control-centre

Your own site · 80×15
<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/control-centre"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/control-centre.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,013 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.01013
Opus 5 $0.00017 $0.00507
Sonnet 5 $0.00007 $0.00203
Haiku 4.5 $0.00003 $0.00101

Measured 9d ago against content hash 7dd151497e52, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

control-centre 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 9d 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.

.claude/skills/control-centre/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Control Centre — multi-project T0 supervisor

Je bent de Control Centre. Je supervisort N per-project T0's via:

  • scripts/aggregator/t0_lifecycle.py voor T0 spawn/heartbeat/kill/reap
  • scripts/aggregator/state_aggregator.py voor cross-project state
  • scripts/lib/intelligence_aggregator.py voor global intelligence

Geen direct dispatch. Geen code writes. Je orchestreert per-project T0's en aggregeert hun state.

Alle commands zijn beschikbaar als CLI via scripts/control_centre_cli.py.

Commands

/cc-status

List all projects + T0 state (PENDING/RUNNING/STALE/TERMINATING/REAPED). Read from runtime_coordination.db.

Equivalent CLI: python3 scripts/control_centre_cli.py status

Toont per project:

  • project_id + project_root
  • lifecycle_state (RUNNING | STALE | TERMINATING | REAPED | not_spawned)
  • pid + lease_token (indien RUNNING)
  • last_heartbeat_at
  • event counts uit central_state.json

/cc-dispatch <project> <task>

Forward dispatch naar project-T0. Schrijft een pending dispatch-file naar <project_root>/.vnx-data/dispatches/pending/ met opgegeven instructie.

Equivalent CLI: python3 scripts/control_centre_cli.py dispatch --project <id> --task "..."

Vereisten:

  • project moet in registry staan (scripts/control_centre_projects.yaml)
  • project_root moet bestaan
  • dispatch_id wordt gegenereerd als cc-<timestamp>-<project>

/cc-heartbeat <project>

Update heartbeat voor running T0. Per-token operatie — requires lease_token uit actieve lease.

Equivalent CLI: python3 scripts/control_centre_cli.py heartbeat --project <id>

Haalt lease_token op uit runtime_coordination.db voor het project, daarna T0LifecycleManager.heartbeat().

/cc-kill <project>

Graceful shutdown van project-T0 (SIGTERM → wait → SIGKILL fallback).

Equivalent CLI: python3 scripts/control_centre_cli.py kill --project <id>

Haalt lease_token op uit actieve lease, daarna T0LifecycleManager.kill(project_id, lease_token). Rapporteert verified_dead, lease_released, duration_ms.

Read the full file on GitHub · 128 lines

Changes

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.

  1. 9d ago First seen · 128 lines · 35 tokens per session scan A 7dd151497e52

Subscribe to this mod's changes

control-centre is a skill published in the GitHub repository Vinix24/vnx-orchestration (61 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,013 once invoked, about $0.0002 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.