analysis-status

analysis-status is a command for Claude Code from with-geun/alive-analysis. It costs 0 tokens per session (449 once invoked), scanned A, original, MIT.

A command that shows a dashboard for analyses currently in progress, recently archived, or waiting to start. It also checks whether the dashboard matches the analysis files on disk.

In plain words
What is it for?
Reviewing active and completed analyses, checking pending work, and finding analyses that are untracked or no longer present.
Why use it?
It makes the state of analysis work visible and points out missing records or outdated entries.

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/with-geun/alive-analysis/analysis-status
Clone the repo
git clone --depth 1 https://github.com/with-geun/alive-analysis

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-status.svg)](https://agentmods.dev/commands/with-geun/alive-analysis/analysis-status)
Your own site
<a href="https://agentmods.dev/commands/with-geun/alive-analysis/analysis-status"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 449 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 $0.00000 $0.00449
Opus 5 $0.00000 $0.00225
Sonnet 5 $0.00000 $0.00090
Haiku 4.5 $0.00000 $0.00045

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

Security

Grade A, and why

analysis-status 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.

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/analysis-status.md · 59 lines

What it actually says

/analysis status

Show current analysis status dashboard.

Instructions

Step 1: Read status.md

Read .analysis/status.md and parse the Active, Recently Archived, and Pending sections.

Step 2: Validate against actual files

Cross-check status.md against actual files in analyses/active/:

  • If a file exists in active/ but not in status.md → warn "untracked analysis"
  • If status.md lists an analysis but file is missing → warn "stale entry"

Step 3: Display dashboard

Format output as a clean dashboard:

═══════════════════════════════════════════════════
  alive-analysis Status Dashboard
═══════════════════════════════════════════════════

  Active Analyses (3)
  ───────────────────
  ❓ F-2026-0210-001  DAU drop investigation     @ye   ASK     [retention, mobile]
  📢 Q-2026-0210-002  Retention check            @ye   VOICE   [retention, onboarding]
  🌱 F-2026-0208-003  Payment funnel analysis    @kim  EVOLVE  [funnel, payment]

  Recently Archived (1)
  ─────────────────────
  ✅ Q-2026-0207-001  Sign-up conversion → "Mobile 30% lower"

  Pending (1)
  ───────────
  ⏳ New user cohort analysis (next week)

═══════════════════════════════════════════════════

Step 4: Stage icons reference

Use these icons for each ALIVE stage:

❓ ASK → 👀 LOOK → 🔍 INVESTIGATE → 📢 VOICE → 🌱 EVOLVE

Completed/archived: ✅ Pending: ⏳

Step 5: Suggestions

Based on the current state, suggest next actions:

  • If any analysis is in VOICE/EVOLVE → "Consider archiving with /analysis archive"
  • If no active analyses → "Start a new analysis with /analysis new"
  • If analyses are stale (>7 days in same stage) → "Consider reviewing stalled analyses"
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 · 59 lines · 0 tokens per session scan A d54e23eab7bf

Subscribe to this mod's changes

analysis-status is a command published in the GitHub repository with-geun/alive-analysis (41 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 449 tokens. 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.