OCTALUME: Command for Claude Code

.claude/commands/lifecycle-phase.md

lifecycle_phase is a command for Claude Code from Harery/OCTALUME. It costs 11 tokens per session (570 once invoked), scanned A, original, MIT.

A command for running one named phase of a project's lifecycle. It checks the phase's prerequisites, performs its documented activities, and records whether the required work and approvals are complete.

In plain words
What is it for?
Use it to execute phases, create their required documents, make go-or-no-go decisions, and update project tracking files.
Why use it?
It gives teams a repeatable way to run a structured project stage and verify that nothing required was skipped.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is Harery/OCTALUME's own configuration. It tells Claude Code how to work on OCTALUME itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything OCTALUME configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Harery/OCTALUME. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Harery/OCTALUME/main/.claude/commands/lifecycle-phase.md
Clone the repo
git clone --depth 1 https://github.com/Harery/OCTALUME

Made for: Claude Code.

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 lifecycle_phase

README.md
[![agentmods](https://agentmods.dev/badge/commands/harery/octalume/lifecycle-phase/github.svg)](https://agentmods.dev/commands/harery/octalume/lifecycle-phase)
Your own site
<a href="https://agentmods.dev/commands/harery/octalume/lifecycle-phase"><img src="https://agentmods.dev/badge/commands/harery/octalume/lifecycle-phase/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 lifecycle_phase

Your own site · 80×15
<a href="https://agentmods.dev/commands/harery/octalume/lifecycle-phase"><img src="https://agentmods.dev/badge/commands/harery/octalume/lifecycle-phase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 570 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.00011 $0.00570
Opus 5.5 $0.00004 $0.00228
Sonnet 5.5 $0.00002 $0.00114
Haiku 4.5 $0.00001 $0.00057

Measured 2mo ago against content hash df51aed8c147, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lifecycle_phase 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 2mo 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/lifecycle-phase.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Execute Lifecycle Phase

Execute Phase $ARGUMENTS of the Unified Enterprise Lifecycle.

Phase Execution Steps

  1. Load Phase Skill: Read the phase-specific SKILL.md file:

    skills/phase_{PHASE_NUMBER}_{PHASE_NAME}/SKILL.md
    
  2. Validate Entry Criteria: Check that all entry criteria are met:

    • Previous phase deliverables complete
    • Required approvals obtained
    • Artifacts created and archived
  3. Read Project State: Load current project state:

    • .claude/project-state.json
    • claude-progress.txt
    • feature_list.json
  4. Execute Phase Activities: Follow the phase workflow:

    • Read phase steps from SKILL.md
    • Execute each step with appropriate owner and participants
    • Create required artifacts
    • Get required approvals
  5. Validate Exit Criteria: Ensure all exit criteria are met:

    • All deliverables complete
    • All artifacts created
    • All approvals obtained
    • Quality gates passed
  6. Go/No-Go Decision: Execute go/no-go decision:

    • Prepare recommendation
    • Get secondary owner review
    • Get executive sponsor approval
    • Document decision
  7. Update Project State: Update all tracking files:

    • Update .claude/project-state.json
    • Update claude-progress.txt
    • Update feature_list.json
    • Archive artifacts to appropriate phase directory
  8. Commit Progress: Commit all work to git:

    git add .
    git commit -m "feat: complete Phase {N} - {PHASE_NAME}
    
    - [Summary of deliverables]
    - [Artifacts created]
    - [Approvals obtained]
    
    Artifacts: P{N}-*
    Phase: phase_{N}_{PHASE_NAME}
    Status: complete
    "
    

Output

Return JSON with:

{
  "phase": "phase_{N}_{PHASE_NAME}",
  "status": "complete",
  "deliverables": ["..."],
  "artifacts": ["P{N}-*", ...],
  "next_phase": "phase_{N+1}_{NEXT_PHASE_NAME}",
  "recommendation": "go/no-go"
}

Important

  • Follow the phase workflow exactly as defined in the SKILL.md
  • Do not skip any steps
  • Get all required approvals
  • Create all required artifacts
  • Update all tracking files
  • Leave the project in a clean state

Read the full file on GitHub · 94 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. 2mo ago First seen · 94 lines · 11 tokens per session scan A df51aed8c147

Subscribe to this mod's changes

lifecycle_phase is a command published in the GitHub repository Harery/OCTALUME (2 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 570 once invoked, about $0.0000 per session on Opus 5.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.