lifecycle_feature

lifecycle_feature is a command for Claude Code from Harery/OCTALUME. It costs 9 tokens per session (749 once invoked), scanned B, original, MIT.

A command for implementing one project feature at a time through planning, coding, testing, and manual checking.

In plain words
What is it for?
Use it to select the highest-priority failing feature, inspect its requirements, plan the files and acceptance checks, implement it, add tests, and verify it manually.
Why use it?
It provides a repeatable way to work through unfinished features without losing track of project status or taking on several changes at once.

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-feature
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_feature

README.md
[![agentmods](https://agentmods.dev/badge/commands/harery/octalume/lifecycle-feature.svg)](https://agentmods.dev/commands/harery/octalume/lifecycle-feature)
Your own site
<a href="https://agentmods.dev/commands/harery/octalume/lifecycle-feature"><img src="https://agentmods.dev/badge/commands/harery/octalume/lifecycle-feature.svg" alt="Measured on agentmods" height="20"></a>
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 749 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00749
Opus 5 $0.00005 $0.00375
Sonnet 5 $0.00002 $0.00150
Haiku 4.5 $0.00001 $0.00075

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

Security

Grade B, and why

lifecycle_feature scanned grade B with 1 finding 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 4d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .claude/project-state.json
.claude/commands/lifecycle-feature.md · 113 lines

How it starts

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

Work on Feature

Work on feature $ARGUMENTS following the incremental development approach.

Feature Workflow

  1. Get Oriented: Start each session by getting oriented:

    pwd
    cat .claude/project-state.json
    cat claude-progress.txt
    git log --oneline -20
    git status
    
  2. Select Feature: Choose ONE feature to work on:

    cat feature_list.json | jq '.features[] | select(.status == "failing")'
    
    • Select the highest priority failing feature (P0 > P1 > P2 > P3)
    • Do NOT work on multiple features in one session
  3. Read Feature Details: Get complete feature information:

    cat feature_list.json | jq ".features[] | select(.id == \"F-XXX\")"
    
  4. Plan Implementation: Create an implementation plan:

    • Current state
    • Changes required
    • Files to modify
    • Acceptance criteria
    • Verification steps
  5. Implement Feature: Write the code:

    • Follow coding standards
    • Write clear comments
    • Handle errors properly
    • Consider security implications
  6. Write Tests: Write comprehensive tests:

    • Unit tests for individual functions
    • Integration tests for component interactions
    • E2E tests for user workflows
  7. Test Manually: Test as a human user would:

    • Start development server: source scripts/init.sh
    • Navigate to the feature
    • Test all acceptance criteria
    • Verify all verification steps
  8. Update Feature Status: Only after thorough testing:

    jq '.features[] |= if .id == "F-XXX" then .status = "passing" else . end' feature_list.json > feature_list.json.tmp
    mv feature_list.json.tmp feature_list.json
    
  9. Commit Progress: Commit to git with descriptive message:

    git add .
    git commit -m "feat: [feature description] (F-XXX)
    
    - [what was done]
    - [tests added]
    - [verification steps completed]
    
    Artifacts: P5-CODE-XXX, P5-TEST-XXX
    Feature: F-XXX
    Status: passing
    "
    
  10. Update Progress: Update claude-progress.txt:

    cat >> claude-progress.txt <<EOF
    
    ### Session N - F-XXX Complete
    **Feature**: [feature description]
    **Status**:  PASSING
    **Tests**: Unit + Integration + E2E
    **Artifacts**: P5-CODE-XXX, P5-TEST-XXX
    EOF
    

Read the full file on GitHub · 113 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. 4d ago First seen · 113 lines · 9 tokens per session scan B fd31c67e42b5

Subscribe to this mod's changes

lifecycle_feature 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 749 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.