lifecycle-audit

Runs black-box lifecycle smoke tests of Mycelium hooks through real Claude Code or Codex CLI tasks.

68|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/arjunrajlaboratory/mycelium --skill lifecycle-audit-arjunrajlaboratory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lifecycle-audit
Source: https://github.com/arjunrajlaboratory/mycelium/tree/main/skills/lifecycle-audit
Command: npx skills add https://github.com/arjunrajlaboratory/mycelium --skill lifecycle-audit-arjunrajlaboratory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After installing or modifying the Mycelium plugin, manually invoking a hook script cannot prove that Claude Code or Codex actually discovered, trusted, and dispatched the hook. This Skill runs a genuine end-to-end lifecycle audit through a real host CLI task, so you can verify SessionStart injection, PostToolUse tracking, Stop enforcement, and handoff generation behave correctly in production-like conditions. ## Core Features & Use Cases - Black-box host verification: Launches a fresh Claude Code or Codex task with a canonical child-task prompt and observes only automatic lifecycle behavior, never invoking hooks manually. - Positive and negative probes: Exercises a harmless analysis command, an argv-rewrite near-neighbor that must stay silent, edit tracking with a disposable file, and the expected Stop-blocking retry with a five-section handoff. - Failure classification: Sorts every unexpected result into artifact identity, host dispatch, hook logic, environment, agent compliance, or inconclusive categories using a structured evidence table. - Use Case: After merging cross-host lifecycle changes, run this audit against a disposable initialized repository to confirm the installed plugin artifact matches the source commit and that nested-subagent isolation, lineage recording, and handoff structure all pass before release. ## Quick Start Use the lifecycle-audit skill to run a black-box Mycelium lifecycle smoke test against a fresh disposable repository in Claude Code and classify any failures.

Frequently Asked Questions about lifecycle-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Mycelium hooks fire in Claude Code or Codex?

Run a black-box lifecycle audit that launches a fresh host CLI task and observes only automatic hook behavior. Manually invoking a hook script cannot prove the host discovered, trusted, and dispatched it, so the audit uses natural SessionStart, PostToolUse, and Stop events as evidence.

How do I test SessionStart and Stop hooks end to end?

Launch one genuinely fresh host task from the exact target root using the canonical child-task prompt, then inspect state only after natural Stop. Verify session markers, the expected Stop block, one compliant retry, and a five-section handoff with exact headings.

Does the lifecycle audit work with both Claude Code and Codex?

Yes, the audit protocol supports both hosts with host-specific substitutions. Claude Code uses Write or Edit tools and the Task subagent mechanism, while Codex uses apply_patch and its native subtask tool, with codex plugin list --json for artifact verification.

Why does the audit fail when hooks seem to work?

A source or cache mismatch between the installed artifact and the source checkout is an audit failure even if hooks fire. Hash exercised installed files against the source candidate and classify failures as artifact identity, host dispatch, hook logic, environment, or agent compliance.

When should I not use the lifecycle audit?

Do not use it as a substitute for unit tests or for ordinary scientific analysis. It is intended for post-installation verification, suspected hook dispatch problems, and pre-merge validation of cross-host lifecycle work, ideally against a disposable repository.