lifecycle_init

A command for starting a new Unified Enterprise Lifecycle project, a structured project process covering planning, development, quality, security, and compliance.

In plain words
What is it for?
Use it to gather project requirements, create folders and configuration, generate a feature list, and initialize project state.
Why use it?
It creates the initial project structure and tracking information needed to manage a large project from its first phase onward.

Command for Claude Code

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.

agentmods
npx agentmods add commands/harery/octalume/lifecycle-init
Clone the repo
git clone --depth 1 https://github.com/Harery/OCTALUME

Made for: Claude Code.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 592 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00009 $0.00592
Opus 5 $0.00005 $0.00296
Sonnet 5 $0.00002 $0.00118
Haiku 4.5 $0.00001 $0.00059

Measured 2d ago against content hash 9a9060bb8df0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

lifecycle_init 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 2d 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-init.md · 92 lines

How it starts

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

Initialize New Lifecycle Project

Please initialize a new Unified Enterprise Lifecycle project with the following requirements:

$ARGUMENTS

Initialization Steps

  1. Gather Requirements: Ask the user for any missing information:

    • Project name
    • Project description
    • Target users
    • Key features
    • Compliance requirements (HIPAA, SOC 2, PCI DSS, GDPR, SOX, etc.)
    • Team members and roles
  2. Create Project Structure: Set up the complete directory structure:

    • .claude/ directory with agent configurations
    • docs/ directory with phase subdirectories
    • src/ directory for source code
    • tests/ directory for tests
    • scripts/ directory for utility scripts
    • artifacts/ directory with phase subdirectories
  3. Generate Feature List: Create a comprehensive feature list:

    • Expand to 200-500 features across all 8 phases
    • Each feature must have clear acceptance criteria
    • Each feature must have verification steps
    • All features start with status "failing"
    • Include governance, security, quality, and compliance features
  4. Initialize Project State: Create .claude/project-state.json:

    • Project metadata
    • Current phase (phase_01_vision_strategy)
    • Phase status (not_started)
    • Artifact counters
    • Team information
    • Compliance information
  5. Set Up Git Repository:

    • Initialize git repository
    • Create .gitignore file
    • Make initial commit
  6. Create init.sh Script: Create scripts/init.sh:

    • Development environment setup
    • Dependency installation
    • Database setup
    • Development server startup
  7. Create Progress Tracking: Create claude-progress.txt:

    • Session history
    • Phase progress
    • Feature progress
  8. Verify Setup: Verify everything is working:

    • Check all directories created
    • Check all files created
    • Verify feature list is comprehensive
    • Test init.sh script

Output

Return JSON with:

{
  "status": "complete",
  "project_name": "...",
  "feature_count": N,
  "next_steps": "Begin Phase 1: Vision & Strategy"
}

Read the full file on GitHub · 92 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. 2d ago First seen · 92 lines · 9 tokens per session scan A 9a9060bb8df0

Subscribe to this mod's changes

lifecycle_init is a command published in the GitHub repository Harery/OCTALUME (2 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 592 once invoked, about $0.0000 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.