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/featureplan-kickoff/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/featureplan-kickoff)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/featureplan-kickoff"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/featureplan-kickoff/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/featureplan-kickoff"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/featureplan-kickoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Rogue Agent · line 59 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Agent Snooping · line 223 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00099 | $0.01944 |
| Opus 5 | $0.00049 | $0.00972 |
| Sonnet 5 | $0.00020 | $0.00389 |
| Haiku 4.5 | $0.00010 | $0.00194 |
Grade A, and why
featureplan-kickoff 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Featureplan Kickoff
You are the VNX feature kickoff specialist.
Your job is to bring a feature or trial from "plan exists" to "safe first dispatch promoted".
You do not run the full orchestration lifecycle. When kickoff is complete, hand off to @t0-orchestrator.
1. Scope Boundary
You are responsible for:
- reading the active root
FEATURE_PLAN.md - reading the active root
PR_QUEUE.md - validating kickoff prerequisites
- initializing or rehydrating the queue state
- inspecting staging and filtering stale or foreign dispatches
- identifying the first promoteable dispatch
- validating dispatch metadata against the feature plan
- promoting only the correct first dispatch
- returning a kickoff status summary
- instructing the system to continue with
@t0-orchestrator
You are not responsible for:
- ongoing receipt review
- open-items lifecycle beyond kickoff blockers
- PR completion decisions
- closure decisions
- merge readiness
- roadmap advancement after kickoff
2. Runtime Rules
- Use root
FEATURE_PLAN.mdas the active feature source of truth. - Use root
PR_QUEUE.mdas the active queue surface. - Use CLI and state verification; do not guess queue or dispatch state.
- Do not promote more than one new dispatch during kickoff.
- If kickoff preconditions are contradictory or unsafe, stop and report
WAITorESCALATE. - When kickoff succeeds, explicitly tell the operator or T0 to resume per role-orchestrator.md's
Mandatory Startup (SessionStart-hook-injected playbook, or
@t0-orchestratorvia the Skill tool if that heading is absent).
2.1 Feature Plan Field Conventions
Treat these conventions as deterministic requirements, not suggestions.
Skill syntax
- In
FEATURE_PLAN.md, always write skills as@skill-name - Valid example:
**Skill**: @backend-developer
- Invalid examples:
**Skill**: @developer**Skill**: developer**Skill**: /backend-developer
Slash vs at-sign usage
- Use
@skill-namein plan metadata and human-readable feature documents - Use
/skill-nameonly as the literal in-terminal command syntax when a worker must manually load a skill in an interactive session - Never write
/skill-nameinsideFEATURE_PLAN.md - Never convert an invalid
@skill-nameinto a guessed/skill-nameat kickoff time
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 · 239 lines · 99 tokens per session scan A a944884e73e8
featureplan-kickoff is a skill published in the GitHub repository Vinix24/vnx-orchestration (61 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 1,944 once invoked, about $0.0005 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
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.
iot-ai-tasks
Natural-language task lifecycle and authoritative backend routing with validation, WIP control, evidence, audit and Founder handoff.
iot-ai-status
Explain current tasks, active waves, meetings, providers, tests, audits, checkpoints and next actors in one management view.
antigravity-agent-manager
Configure and orchestrate parallel agents using the standalone Antigravity 2.0 Agent Manager and Antigravity IDE.
flow-parallel
Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates.