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/estate-steward.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/estate-steward)<a href="https://agentmods.dev/commands/frankxai/starlight-intelligence-system/estate-steward"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/estate-steward/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/estate-steward"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/estate-steward.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.01304 |
| Opus 5 | $0.00000 | $0.00652 |
| Sonnet 5 | $0.00000 | $0.00261 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
estate-steward 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/estate-steward
Load the estate's 4-layer Blueprint, SIS-instance.md, current harness configs, and the commissioning workflow docs. Configure or invoke the Steward layer for the Standing phase (after Pilot/Scale handover).
Steward is the "run the army reliably and evolve it" role — the annuity in the factory economics. It turns a built estate into a living, compounding system the client (or their operator) can own and operate.
Input
$ARGUMENTS
Subcommands
setup (default if no subcommand)
- Wire the production Steward primitives into the estate:
- Health monitoring (drift detection, scheduled Proving Ground / Model Arena on the client's specific patterns, token efficiency, routing accuracy).
- Memory hygiene (temporal half-life enforcement, contradiction sweeps, dreaming promotion, Veil audits).
- Self-healing triggers (claws for reclamation, attestation repair, harness re-sync).
- Evolution hooks (new module spawn suggestions, topology tweak recommendations, /sis-forge extraction points).
- Reporting cadence (monthly health report template tied to the world-class E2E checklist).
- Board facilitation (reminders and scaffolding for /starlight-board on major moves).
- Create or update
steward/dir or equivalent (runbooks, dashboards config, cron/task definitions). - Seed the first health baseline from the Pilot phase metrics.
- Output: Updated configs + "Steward is now active" summary with next report date.
health
- Run a full current-state health check against the estate's Mesh + Mind.
- Use existing claws (sentinel, attestation, memory maintenance) + orchestrator self-learning loops + evals.
- Compare against the world-class E2E checklist (client can describe behavior, live attested work without babysitting, memory compounds, client can evolve via runbooks, gates held, measurable tech metrics).
- Output: Health report (JSON + human summary) + any immediate remediation suggestions.
evolve
- Propose and (with confirmation) apply evolution steps:
- New domain sub-stack or module (via /spawn-domain-stack patterns, grounded in the estate's Genius KEEP items).
- Topology or kernel adjustment (always surface board gate if high-stakes).
- Harness / /si routing improvements from the upgrades track.
- Promotion of any newly generalized patterns back to the starlight-estate-os profile.
- Requires the estate's current 4-layer Blueprint + recent health data.
- Output: Evolution plan + (optional) applied changes + updated Blueprint if the 4-layer shifted.
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 · 109 lines · 0 tokens per session scan A 1111d616ab70
estate-steward 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 1,304 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
memories
View and manage learned memories.
mpm-session-resume
Load context from paused session.
forget
Delete specific memories.
learn
Add new learning to memory.
gbu-retro
Post-session retrospective — harvest this session's lessons into durable doctrine.
consolidate
Write a compact checkpoint summary of the current frontier.