Borrowing it
Nothing to install: this file belongs to frankxai/Starlight-Intelligence-System. 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/frankxai/Starlight-Intelligence-System/main/.claude/commands/org-succession.mdgit clone --depth 1 https://github.com/frankxai/Starlight-Intelligence-SystemWrote 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/commands/frankxai/starlight-intelligence-system/org-succession)<a href="https://agentmods.dev/commands/frankxai/starlight-intelligence-system/org-succession"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/org-succession/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/commands/frankxai/starlight-intelligence-system/org-succession"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/org-succession.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.00000 | $0.02939 |
| Opus 5 | $0.00000 | $0.01470 |
| Sonnet 5 | $0.00000 | $0.00588 |
| Haiku 4.5 | $0.00000 | $0.00294 |
Grade A, and why
org-succession 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 11d 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.
/org-succession
Load SIP.md, agents/starlight-org.md, skills/people-intelligence/org-architecture.md. Read any prior people-intelligence/org/ outputs. Produce a Succession Architecture document. Hand off to exactly one next command.
Disclaimer (non-waivable)
Succession planning implicates compensation discussions, promotion decisions, classification (exempt/non-exempt status changes), and protected-class considerations in promotion patterns. This is structural thinking architecture, not employment-law advice. Real promotion / role-change decisions require qualified employment counsel.
The honest opening
Most companies have succession plans on paper and no actual readiness on the bench. Real succession planning is measurable: a named successor exists, a development plan exists with named gaps closing on a schedule, the successor has actually performed parts of the role under controlled conditions, a timeline is real and named, and the successor has been told. Anything missing any of those = paper, not readiness. This command refuses paper.
Input
$ARGUMENTS
Flags
--critical-roles <comma-separated list>— which roles to plan for. If unsure, run/org-role-designfirst or list the roles where the org would be in real trouble within 30 days of the incumbent leaving (that's the working definition of "critical").--horizon <12mo|3yr|5yr>:12mo— near-term continuity (illness, departure, parental leave, bus-factor)3yr— strategic succession (founder evolution, scale-driven layer shifts, planned exits)5yr— generational succession (founder transition, exec retirement, long-arc development)
Process
-
Disclaim.
-
Open with the readiness honesty. Most plans are paper. Name what real readiness requires.
-
Critical role inventory. For each role on the list:
- Why is it critical? (decision-rights concentration, irreplaceable institutional knowledge, customer-facing identity, regulatory/license-holding, etc.)
- 30-day risk: what breaks if the incumbent leaves tomorrow?
- 90-day risk: what compounds if no one is named in 90 days?
- 12-month risk: what strategic capability is lost without succession?
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.
- 11d ago First seen · 239 lines · 0 tokens per session scan A 3ebb9d7d7b7b
org-succession is a command published in the GitHub repository frankxai/Starlight-Intelligence-System (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,939 tokens. 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-31.
Other commands, from other repositories
lavra-checkpoint
Save session progress by filing beads, capturing knowledge, and syncing state.
bigproject
Large-scale project orchestration with Himawari (Atlas).
memories
View and manage learned memories.
mpm-init
Initialize or update project for Claude Code and MPM.
mpm-organize
Organize project files with intelligent consolidation.
mpm-ticket-view
Orchestrate ticketing agent for project management workflows.