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/planner/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/planner)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/planner"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/planner/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/planner"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 163 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00111 | $0.01600 |
| Opus 5 | $0.00056 | $0.00800 |
| Sonnet 5 | $0.00022 | $0.00320 |
| Haiku 4.5 | $0.00011 | $0.00160 |
Grade B, and why
planner scanned grade B 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
## Output Instructions How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Specialist
Generate structured FEATURE_PLAN.md documents with PR-based breakdown for T0 orchestration.
Core Responsibilities
- Break features into reviewable PRs (150-300 lines each)
- Define clear PR dependencies and execution order
- Map skills to specific PRs
- Validate PR size constraints
- Ensure acyclic dependency graphs
- Write quality gates that become trackable deliverables (see Governance Model)
Planning Process
- Analyze Requirements: Break down into testable requirements
- PR Decomposition: Split into 150-300 line PRs with clear scope
- Skill Assignment: Map appropriate @skill to each PR
- Dependency Mapping: Define PR execution order (must be acyclic)
- Size Validation: Verify all PRs within 150-300 line constraint
- Quality Gates: Define verification criteria per PR using checklist format
Governance Model: Quality Gates as Deliverables
Quality gate items become open items when init-feature runs. Each checklist item is tracked individually with a severity level. T0 (the orchestrator) is the sole authority for declaring work done — the performing terminal never auto-completes its own PR.
Flow:
FEATURE_PLAN.md quality gates
→ init-feature parses checklist items
→ creates open items (OI-PRx-001, OI-PRx-002, ...)
→ terminal executes work, receipt records evidence
→ T0 reviews evidence, closes satisfied items
→ all blockers/warns closed → PR complete
This means every quality gate item you write will be individually tracked. Write them to be:
- Specific: "All 405 tests pass" not "Tests pass"
- Measurable: Include numbers, thresholds, or binary criteria
- Verifiable: T0 must be able to evaluate evidence against the criterion
Quality Gate Severity Classification
Items are auto-classified by init-feature based on keywords:
| Severity | Keywords | Example |
|---|---|---|
blocker |
"all tests pass", "E2E", "100%", "test suite passes" | - [ ] All tests pass |
warn |
"memory", "zombie", "regression", ">=", "shutdown", "speed" | - [ ] Memory profiling: no regression |
info |
Default (anything else) | - [ ] Dashboard shows accurate data |
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 · 180 lines · 111 tokens per session scan B d0614201ff39
planner is a skill published in the GitHub repository Vinix24/vnx-orchestration (61 stars, last pushed yesterday), licensed MIT. It adds 111 tokens to every session and 1,600 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). 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…