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.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/instructions/vinix24/vnx-orchestration/claude-md)<a href="https://agentmods.dev/instructions/vinix24/vnx-orchestration/claude-md"><img src="https://agentmods.dev/badge/instructions/vinix24/vnx-orchestration/claude-md/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/instructions/vinix24/vnx-orchestration/claude-md"><img src="https://agentmods.dev/badge/instructions/vinix24/vnx-orchestration/claude-md.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.02220 | $0.02220 |
| Opus 5 | $0.01110 | $0.01110 |
| Sonnet 5 | $0.00444 | $0.00444 |
| Haiku 4.5 | $0.00222 | $0.00222 |
Grade A, and why
vnx-orchestration CLAUDE.md scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **`scripts/lib/subprocess_dispatch.py`** — terminal-pinned (Wave 5 smart-context, lease, triple-gate). Opt in per terminal with `VNX_ADAPTER_T{n}=subprocess`. Use for single-worker PRs that benefit from prior-round fin How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VNX Governance
This repository is governed by VNX Glass Box Governance: multi-agent orchestration with a human gate at every step and an append-only NDJSON receipt per dispatch.
The mechanism is not duplicated here. How the fabric works — the single-entry dispatch door and its lanes, review gates, the horizon planning layer, state resolution, and the report contract — lives in one canonical place so it can never drift out of a project file:
- How the fabric works: the canonical orchestrator role,
.claude/terminals/T0/role-orchestrator.md, kept in sync fleet-wide byvnx role sync. - Runbooks + gotchas: the
fabric-referenceskill. - Dispatch mechanics (lanes, provider routing, failure modes):
docs/core/DISPATCH_RULES.md.
Everything above this block describes this project. Everything the fabric does lives in the canonical role — never copy fabric mechanism back into this file, or the copy drifts the moment the fabric changes.
Mandatory Report Contract
Every agent and worker MUST write a unified report on completing any task.
This is how work enters the governed audit trail:
report on disk → receipt processor → t0_receipts.ndjson
Without a report, your work has no receipt and is invisible to governance.
Write to: $VNX_DATA_DIR/unified_reports/<dispatch-id>.md
Your report MUST contain these exact headings (aliases accepted):
| Required | Accepted aliases |
|---|---|
## Summary |
— |
## Changes |
## Files Modified, ## Work Completed |
## Verification |
## Test Results, ## Evidence, ## Tests |
## Open Items |
— |
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.
- 9d ago First seen · 123 lines · 2,220 tokens per session scan A d89d74e59a7b
vnx-orchestration CLAUDE.md is an instructions file published in the GitHub repository Vinix24/vnx-orchestration (61 stars, last pushed today), licensed MIT. It adds 2,220 tokens to every session, about $0.0111 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.