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.
curl -O https://raw.githubusercontent.com/Harery/OCTALUME/main/.claude/commands/lifecycle-init.mdgit clone --depth 1 https://github.com/Harery/OCTALUMEWrote 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/harery/octalume/lifecycle-init)<a href="https://agentmods.dev/commands/harery/octalume/lifecycle-init"><img src="https://agentmods.dev/badge/commands/harery/octalume/lifecycle-init/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/harery/octalume/lifecycle-init"><img src="https://agentmods.dev/badge/commands/harery/octalume/lifecycle-init.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.00009 | $0.00592 |
| Opus 5.5 | $0.00004 | $0.00237 |
| Sonnet 5.5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
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 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.
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
-
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
-
Create Project Structure: Set up the complete directory structure:
.claude/directory with agent configurationsdocs/directory with phase subdirectoriessrc/directory for source codetests/directory for testsscripts/directory for utility scriptsartifacts/directory with phase subdirectories
-
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
-
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
-
Set Up Git Repository:
- Initialize git repository
- Create
.gitignorefile - Make initial commit
-
Create init.sh Script: Create
scripts/init.sh:- Development environment setup
- Dependency installation
- Database setup
- Development server startup
-
Create Progress Tracking: Create
claude-progress.txt:- Session history
- Phase progress
- Feature progress
-
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"
}
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.
- 2mo ago First seen · 92 lines · 9 tokens per session scan A 9a9060bb8df0
lifecycle_init is a command published in the GitHub repository Harery/OCTALUME (2 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 592 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.
Other commands, from other repositories
operator-dispatch
The dispatch session role: a model-less host. Its hierarchy hooks module runs the tick, consumes verdicts and PR events, renders the board pane and wakes executors. Never answers a design decision, never touches main.
dispatch-worker
Retired Pattern Z Worker loop; use cli-hierarchy (RFC-0051) instead. See docs/operations/cli-hierarchy.md. AISDLC-763.
execute-parallel-status
Retired parallel status table; use cli-hierarchy (RFC-0051) instead. See docs/operations/cli-hierarchy.md. AISDLC-763.
backlog
Generate prioritised product backlog from ArcKit artifacts - convert requirements to user stories, organise into sprints.
service-assessment
Prepare for GDS Service Standard assessment - analyze evidence against 14 points, identify gaps, generate readiness report.
story
Generate comprehensive project story with timeline analysis, traceability, and governance achievements (project).