Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git 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/alliance-reflect)<a href="https://agentmods.dev/commands/frankxai/starlight-intelligence-system/alliance-reflect"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/alliance-reflect/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/alliance-reflect"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/alliance-reflect.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.00031 | $0.00764 |
| Opus 5 | $0.00015 | $0.00382 |
| Sonnet 5 | $0.00006 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
alliance-reflect 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 10d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/alliance-reflect
Load the alliance's SKILL.md, AGENTS.md, MEMORY.md, and SIP.md (protocol spec). Facilitate the cycle reflection.
Cycle focus
$ARGUMENTS
Process
-
Pull state.
- Notion alliance DB (ID in
MEMORY.md) for last closed cycle. - GitHub across all member repos (per
MEMORY.mdnode declarations) for commits since last cycle close. - Any vertical MCPs in play (e.g.,
arcanea-mcp.canon-validatefor canon updates).
- Notion alliance DB (ID in
-
Each node reports. First-person voice from the node's frame. ≤5 sentences. If a node shipped nothing, one sentence naming that fact — do not fabricate activity. Silence is reported, not hidden.
-
Surface dependencies. Name blocking handoffs explicitly: "[Node A] blocks [Node B] on [artifact] until [date]." If a dependency reveals a structural fork, emit:
→ run /alliance-decide "<fork statement>"and continue. -
Extract commitments. Each node names exactly ONE artifact for next cycle. Format: artifact name + date. Reject "I will explore" — only "I will ship X by Y."
-
Synthesizer closes. The overseer voice (or designated synthesizer) speaks last. ≤3 sentences. What the alliance must protect or advance next. Not a summary — a synthesis.
-
Writeback.
- Append to Notion alliance DB as new cycle entry.
- Update
MEMORY.md§ Active commitments table. - Update
MEMORY.md§ Open forks if new forks surfaced.
Output shape
# Alliance Reflection — <alliance-name> · Cycle <N>
**Focus:** <cycle focus>
**Opened:** <date> · **Closes:** <date>
## <node-1> speaks (<role>)
[≤5 sentences, first person]
## <node-2> speaks (<role>)
[≤5 sentences, first person]
[… for each node …]
## Dependencies
- <Node A> blocks <Node B> on <artifact> until <date>
- …
## Forks surfaced
- <fork statement> → /alliance-decide
- …
## Commitments — Cycle <N+1>
- <node-1>: <artifact> by <date>
- <node-2>: <artifact> by <date>
- …
## Synthesis (<synthesizer>)
[≤3 sentences]
---
**Built on SIP** · <alliance-name> · Cycle <N> · <date>
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.
- 10d ago First seen · 78 lines · 31 tokens per session scan A 95937f0d2d1e
alliance-reflect is a command published in the GitHub repository frankxai/Starlight-Intelligence-System (8 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 764 once invoked, about $0.0002 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-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.