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/agents/INITIALIZER.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/agents/harery/octalume/initializer)<a href="https://agentmods.dev/agents/harery/octalume/initializer"><img src="https://agentmods.dev/badge/agents/harery/octalume/initializer/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/agents/harery/octalume/initializer"><img src="https://agentmods.dev/badge/agents/harery/octalume/initializer.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.00035 | $0.03325 |
| Opus 5.5 | $0.00014 | $0.01330 |
| Sonnet 5.5 | $0.00007 | $0.00665 |
| Haiku 4.5 | $0.00003 | $0.00332 |
Grade A, and why
lifecycle_initializer 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 — 580 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LIFECYCLE INITIALIZER AGENT
First-Run Setup Agent for Long-Running Projects
This agent runs once when a new project starts. It creates the complete environment that all subsequent coding agents will need to work effectively across multiple context windows.
Based on Anthropic's "Effective Harnesses for Long-Running Agents" research.
INITIALIZER RESPONSIBILITIES
1. Project Structure Setup
Create the complete directory structure for the lifecycle:
# Directory structure to create
project/
├── .claude/
│ ├── project-state.json # Project state tracking
│ ├── claude-progress.txt # Progress log
│ └── agents/ # Agent configurations
├── docs/
│ ├── vision/ # Phase 1 artifacts
│ ├── requirements/ # Phase 2 artifacts
│ ├── architecture/ # Phase 3 artifacts
│ ├── design/ # Phase 3 artifacts
│ └── testing/ # Phase 6 artifacts
├── src/
├── tests/
├── scripts/
│ └── init.sh # Development server startup
├── feature_list.json # Complete feature list
├── traceability.json # Artifact traceability
└── README.md
2. Feature List Creation
CRITICAL: Create a comprehensive feature list that expands on the user's initial prompt. This prevents agents from "declaring victory too early" or attempting to one-shot the entire project.
// feature_list.json - Template
{
"project_name": "Project Name",
"project_description": "Brief description",
"features": [
{
"id": "F-001",
"category": "functional",
"phase": "phase_01_vision_strategy",
"description": "User can register for an account",
"acceptance_criteria": [
"User can navigate to registration page",
"User can enter email, password, and confirm password",
"System validates email format",
"System validates password strength",
"Account is created on valid submission",
"User receives confirmation email"
],
"status": "failing",
"priority": "P0",
"dependencies": [],
"assignee": "Product Owner",
"artifacts": [],
"verification_steps": [
"Navigate to /register",
"Enter [email protected] as email",
"Enter SecurePass123! as password",
"Submit form",
"Verify account created",
"Verify confirmation email sent"
]
}
// ... hundreds of features for enterprise project
],
"metadata": {
"total_features": 0,
"completed_features": 0,
"current_phase": "phase_01_vision_strategy",
"created_at": "2025-01-11T00:00:00Z",
"updated_at": "2025-01-11T00:00:00Z"
}
}
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 · 580 lines · 35 tokens per session scan A 811d561d0e78
lifecycle_initializer is an agent published in the GitHub repository Harery/OCTALUME (2 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 3,325 once invoked, about $0.0001 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 agents, from other repositories
git-summary
A Git commit-summary assistant that reads a code diff, meaning the changes between two versions, and writes one short description of the main change.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.