alive-analysis

alive-analysis is a skill for Claude Code, Codex from with-geun/alive-analysis. It costs 25 tokens per session (21,909 once invoked), scanned A, a copy of alive-analysis, MIT.

A structured data-analysis workflow based on ALIVE: Ask, Look, Investigate, Voice, and Evolve. It supports both analysts and people in roles such as engineering, product, and marketing.

In plain words
What is it for?
Use it to clarify the real question, inspect data, test causes or relationships, communicate findings, and improve the analysis through iteration.
Why use it?
It helps turn a vague data question into a defined investigation with clear scope, hypotheses, and conclusions.

Skill for Claude CodeCodex

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 skills/with-geun/alive-analysis/claude-code
Any agent
npx skills add with-geun/alive-analysis --skill claude-code
Clone the repo
git clone --depth 1 https://github.com/with-geun/alive-analysis

Made for: Claude Code, Codex.

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 alive-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/with-geun/alive-analysis/claude-code.svg)](https://agentmods.dev/skills/with-geun/alive-analysis/claude-code)
Your own site
<a href="https://agentmods.dev/skills/with-geun/alive-analysis/claude-code"><img src="https://agentmods.dev/badge/skills/with-geun/alive-analysis/claude-code.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 21,909 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% copy Near-identical to another mod 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.00025 $0.21909
Opus 5 $0.00013 $0.10955
Sonnet 5 $0.00005 $0.04382
Haiku 4.5 $0.00003 $0.02191

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

Security

Grade A, and why

alive-analysis 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 4d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (hooks/post-analysis-action.sh, hooks/session-start.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

91% identical to alive-analysis — 106 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

platforms/claude-code/SKILL.md · 1,989 lines

How it starts

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

alive-analysis Skill

Data analysis workflow kit based on the ALIVE loop. Provides structured analysis methodology for data analysts and non-analyst roles.


Overview

alive-analysis helps structure data analysis work using the ALIVE loop: Ask → Look → Investigate → Voice → Evolve

It serves two personas:

  • Data analysts: Deep, systematic analysis with full ALIVE flow
  • Non-analyst roles (PM, engineers, marketers): Quick analysis with guided framework

ALIVE Loop Reference

Stage 1: ASK (❓)

Core question: What do we want to know — and WHY?

Purpose:

  • Define the problem clearly and confirm the requester's REAL goal (not just what they said)
  • Frame the question: Is this about causation ("Why did X happen?") or correlation ("Are X and Y related?")?
  • Set success criteria and scope boundaries
  • Build a hypothesis tree before touching any data
  • Set up multi-lens perspective: macro (market/industry) → meso (company/product) → micro (user/session)
Hypothesis Tree

Before diving into data, structure thinking:

Main question: "Why did D30 retention drop?"
├── Internal factors
│   ├── Product changes (releases, feature removals)
│   ├── Channel mix changes (acquisition source shift)
│   ├── Cross-service impact (did another service change affect this?)
│   └── Pricing / promotion changes
├── External factors
│   ├── Seasonality / holidays
│   ├── Competitor actions
│   ├── Market / economic shifts
│   └── Platform changes (iOS/Android policy, algorithm updates)
└── Data artifacts
    ├── Tracking changes (instrumentation broke?)
    ├── Definition changes (metric recalculated?)
    └── Population changes (new user mix shifted?)
Causal vs Correlational Framing

Ask explicitly:

  • "Are we trying to prove X caused Y? Or just that they move together?"
  • "If we find a correlation, what would we need to prove causation?"
  • This determines the methodology: correlation → observational analysis; causation → quasi-experimental or controlled experiment

Read the full file on GitHub · 1,989 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 · 1,989 lines · 25 tokens per session scan A 81571042b554

Subscribe to this mod's changes

alive-analysis is a skill published in the GitHub repository with-geun/alive-analysis (41 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 21,909 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to alive-analysis, differing in 106 lines, and is treated as a copy.