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.
git 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/commands/with-geun/alive-analysis/analysis-status)<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/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/commands/with-geun/alive-analysis/analysis-status"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-status.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.00000 | $0.00449 |
| Opus 5.5 | $0.00000 | $0.00180 |
| Sonnet 5.5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
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 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.
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"
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 · 59 lines · 0 tokens per session scan A d54e23eab7bf
analysis-status is a command published in the GitHub repository with-geun/alive-analysis (41 stars, last pushed 4mo 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.
Other commands, from other repositories
project_init
A command that starts tracking a project with ocul-pm by creating its project records and agent logging rules.
standup
A command that creates a daily stand-up report from an ocul-pm project's work logs and plan. A stand-up is a short update on completed work, blocked work, and next steps.
inception
A command for starting the design of a new project or major feature area. It guides research, agreement on the specification, a detailed three-level plan, evaluation checks, and initial project rules.
start-shopify-app
Start a beginner-friendly Shopify app project from idea or an existing repository.
add-webhook
Add a reliable authenticated Shopify event handler and test failure cases.
audit-scopes
Audit Shopify scopes and protected-data access without expanding permissions.