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.
npx skills add with-geun/alive-analysis --skill claude-codegit clone --depth 1 https://github.com/with-geun/alive-analysisWrote 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/skills/with-geun/alive-analysis/claude-code)<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/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/skills/with-geun/alive-analysis/claude-code"><img src="https://agentmods.dev/badge/skills/with-geun/alive-analysis/claude-code.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.00025 | $0.21909 |
| Opus 5.5 | $0.00010 | $0.08764 |
| Sonnet 5.5 | $0.00005 | $0.04382 |
| Haiku 4.5 | $0.00003 | $0.02191 |
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 1mo 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.
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.
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
What ships with it
26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- commands/analysis-agent.md 4.2 KB
- commands/analysis-archive.md 2.9 KB
- commands/analysis-dr.md 7.2 KB
- commands/analysis-init.md 9.8 KB
- commands/analysis-learn-hint.md 1.9 KB
- commands/analysis-learn-next.md 4.7 KB
- commands/analysis-learn-review.md 5.3 KB
- commands/analysis-learn.md 4.6 KB
- commands/analysis-list.md 2.9 KB
- commands/analysis-new.md 26 KB
- commands/analysis-next.md 15 KB
- commands/analysis-promote.md 5.2 KB
- commands/analysis-retro.md 5.6 KB
- commands/analysis-search.md 5.8 KB
- commands/analysis-status.md 2.1 KB
- commands/analysis-wiki.md 7.2 KB
- commands/experiment-archive.md 2.7 KB
- commands/experiment-new.md 10 KB
- commands/experiment-next.md 14 KB
- commands/model-register.md 4.5 KB
- commands/monitor-check.md 5.9 KB
- commands/monitor-list.md 3.0 KB
- commands/monitor-setup.md 6.1 KB
- hooks/hooks.json 699 B
- hooks/post-analysis-action.sh 634 B runs code
- hooks/session-start.sh 2.1 KB runs code
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.
- 1mo ago First seen · 1,989 lines · 25 tokens per session scan A 81571042b554
alive-analysis is a skill published in the GitHub repository with-geun/alive-analysis (41 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 21,909 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
A/B Test Validation
Validating A/B test implementations including traffic splitting accuracy, statistical significance calculation, metric tracking, and experiment cleanup.
oculpm-journal
A work-journal format for recording coding-agent tasks, including bugs, features, errors, refactors, and chores. It defines where files go and what information each record must contain.
self-audit
A self-check procedure for reviewing work before calling it complete, including requirements, tests, and the final change list.
memory
Project memory management. Modes: (1) 'recall' — project-memory recall when session context is needed, (2) 'update' — project memory evaluation before git commit, (3) 'consolidate' — merge redundant entries and retire outdated ones.
adr-creator
Create or revise Architecture Decision Records (ADR) documenting key technical decisions. Use ONLY when invoked by the memory skill after it has decided an ADR write is needed. This skill is a pure writer - it does NOT decide whether to write. It receives a write verdict (CREATE, UPDATE, or SUPERSEDE) plus context…
git-commit
Automated git commit workflow with intelligent commit message generation and memory management. Use when the user requests to commit code changes (e.g., "/git-commit", "commit my changes", "commit this work"). Generates English Conventional Commit messages in the required : AI format, invokes memory update for…