alliance-reflect

alliance-reflect is a command for Claude Code from frankxai/Starlight-Intelligence-System. It costs 31 tokens per session (764 once invoked), scanned A, original, MIT.

A cycle review for a group of connected projects or teams. It gathers each member’s progress, dependencies, and one concrete promise for the next work cycle.

In plain words
What is it for?
Use it at the end of a cycle to check shared project records and code changes, record what each team shipped, identify blockers, and agree on the next deliverables.
Why use it?
It makes unfinished work, blocked handoffs, and unclear commitments visible instead of leaving them scattered across tools.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions AGENTS.md.

Part of the starlight-intelligence-system plugin — 6 skills, 121 commands, 7 agents shipped together

Good fit Use it at the end of a cycle to check shared project records and code changes, record what each team shipped, identify blockers, and agree on the next deliverables.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/frankxai/starlight-intelligence-system/alliance-reflect
Install

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.

Clone the repo
git clone --depth 1 https://github.com/frankxai/Starlight-Intelligence-System

Made for: Claude Code.

Or install starlight-intelligence-system, the plugin that ships this one along with the rest of its 6 skills, 121 commands, 7 agents.

Wrote 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.

agentmods badge for alliance-reflect

README.md
[![agentmods](https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/alliance-reflect/github.svg)](https://agentmods.dev/commands/frankxai/starlight-intelligence-system/alliance-reflect)
Your own site
<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.

agentmods 80×15 button for alliance-reflect

Your own site · 80×15
<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>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 764 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 10d ago against content hash 95937f0d2d1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

.claude/commands/alliance-reflect.md · 78 lines

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

  1. Pull state.

    • Notion alliance DB (ID in MEMORY.md) for last closed cycle.
    • GitHub across all member repos (per MEMORY.md node declarations) for commits since last cycle close.
    • Any vertical MCPs in play (e.g., arcanea-mcp.canon-validate for canon updates).
  2. 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.

  3. 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.

  4. 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."

  5. 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.

  6. 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>

Read the full file on GitHub · 78 lines

Changes

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.

  1. 10d ago First seen · 78 lines · 31 tokens per session scan A 95937f0d2d1e

Subscribe to this mod's changes

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.