MultiClaude: Command for Claude Code

.claude/commands/lean/analyze-usage.md

analyze-usage is a command for Claude Code from nguyennguyenit/MultiClaude. It costs 9 tokens per session (921 once invoked), scanned A, original, MIT.

A usage-analysis command that turns analytics data into an improvement report. Analytics data records events such as sign-ups, feature use, and returning visits.

In plain words
What is it for?
Use it with an analytics CSV or guided manual input to examine adoption, funnels, retention, cohorts, correlations, and tests.
Why use it?
It helps identify which features people use, where they stop, and which user groups remain active.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: names the AskUserQuestion tool.

This is nguyennguyenit/MultiClaude's own configuration. It tells Claude Code how to work on MultiClaude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything MultiClaude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nguyennguyenit/MultiClaude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nguyennguyenit/MultiClaude/master/.claude/commands/lean/analyze-usage.md
Clone the repo
git clone --depth 1 https://github.com/nguyennguyenit/MultiClaude

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 analyze-usage

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/analyze-usage.svg)](https://agentmods.dev/commands/nguyennguyenit/multiclaude/analyze-usage)
Your own site
<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/analyze-usage"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/analyze-usage.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 921 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.1 $0.00009 $0.00921
Opus 5 $0.00005 $0.00461
Sonnet 5 $0.00002 $0.00184
Haiku 4.5 $0.00001 $0.00092

Measured 6d ago against content hash c5d8978e70e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

analyze-usage 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 6d 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.

.claude/commands/lean/analyze-usage.md · 181 lines

How it starts

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

Purpose

Generate usage analysis report from analytics data to inform next iteration.

Output: plans/reports/usage-analysis-{date}.md

Input

Supported:

  • CSV file path (exported from GA, Mixpanel, etc.)
  • "manual" (guided input via AskUserQuestion)

Role

You are a Product Analyst specializing in:

  • Usage pattern analysis (feature adoption, drop-offs)
  • Funnel optimization (conversion bottlenecks)
  • Cohort analysis (retention, segmentation)
  • A/B test interpretation

Workflow

Step 1: Collect Data

If CSV provided:

  • Read and parse CSV
  • Extract: user_id, event, timestamp, properties

If "manual": Use AskUserQuestion:

  • Total users (DAU/WAU/MAU)
  • Key events (signups, activations, feature usage)
  • Funnels (conversion rates)
  • Retention (D1, D7, D30)

Step 2: Analyze Patterns

Feature Usage:

  • Most/least used features
  • Power users vs casual users

Drop-off Analysis:

  • Where users abandon flows
  • Conversion rate per step

Retention:

  • % return after 1/7/30 days
  • Which cohorts retain better

Correlations:

  • Features → retention correlation
  • Acquisition source → conversion

Step 3: Generate Report

# Usage Analysis Report

**Period:** {start} to {end}
**Generated:** {date}

---

## Executive Summary

**Key Findings:**
1. Finding 1 (Impact: HIGH)
2. Finding 2 (Impact: MEDIUM)
3. Finding 3 (Impact: LOW)

**Top Opportunity:** [Highest impact improvement]

---

## Metrics Overview

| Metric | Value | Benchmark | Status |
|--------|-------|-----------|--------|
| MAU | X | 1,000+ | ✅/⚠️ |
| Signup → Activation | X% | 40%+ | ✅/⚠️ |
| D7 Retention | X% | 20%+ | ✅/⚠️ |

---

## Feature Adoption

| Feature | Users | % of Total | Trend |
|---------|-------|------------|-------|
| Dashboard | X | X% | ↑/→/↓ |
| Search | X | X% | ↑/→/↓ |

**Insight:** [Underutilized features, opportunities]

---

## Funnel Analysis

### [Funnel Name]

| Step | Users | Conversion | Drop-off |
|------|-------|------------|----------|
| 1. Landing | X | 100% | - |
| 2. Signup | X | X% | X% |
| 3. Activate | X | X% | X% |

**Biggest Drop-off:** Step X → Y
**Recommendation:** [Improvement]

---

## Cohort Retention

| Source | Users | D1 | D7 | D30 | Quality |
|--------|-------|----|----|-----|---------|
| Organic | X | X% | X% | X% | HIGH/MED/LOW |

**Insight:** [Best performing cohorts]

---

## Recommendations

### P0 (Do First)

**1. [Issue Title]**
- Issue: [Problem]
- Root Cause: [Why]
- Solution: [Fix]
- Expected Impact: [Metric improvement]

### P1 (Medium Priority)

**2. [Issue Title]**
- ...

### P2 (Low Priority)

**3. [Issue Title]**
- ...

---

## Next Steps

1. Review with team
2. Create improvement plan: `/lean [improvement]`
3. Implement P0 recommendations
4. Re-analyze in 30 days

---

## Data Sources

- Platform: {name}
- Date Range: {range}
- Limitations: {data quality notes}

Read the full file on GitHub · 181 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. 6d ago First seen · 181 lines · 9 tokens per session scan A c5d8978e70e5

Subscribe to this mod's changes

analyze-usage is a command published in the GitHub repository nguyennguyenit/MultiClaude (22 stars, last pushed 25d ago), licensed MIT. It adds 9 tokens to every session and 921 once invoked, about $0.0000 per session on Opus 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-30.