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 agentmods add commands/with-geun/alive-analysis/analysis-newgit 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-new)<a href="https://agentmods.dev/commands/with-geun/alive-analysis/analysis-new"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-new.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.06506 |
| Opus 5 | $0.00000 | $0.03253 |
| Sonnet 5 | $0.00000 | $0.01301 |
| Haiku 4.5 | $0.00000 | $0.00651 |
Grade A, and why
analysis-new 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.
How it starts
The opening of the file, as written. The whole thing — 848 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analysis new
Start a new analysis. Supports --from {Quick ID} for Quick-to-Full succession and --from-alert {Alert ID} for monitor alert escalation.
Instructions
Step 1: Check initialization
Verify .analysis/config.md exists. If not, tell the user to run /analysis init first.
Read config.md to load team context (metrics, stakeholders, data stack).
Step 2: Parse arguments
- If
--from-alert {Alert ID}is provided, this is a monitor alert escalation (skip to Step 2d) - If
--from {ID}is provided, this is a Quick→Full succession (skip to Step 2c) - Otherwise, proceed to Step 2a
Step 2a: Ask analysis type
Use AskUserQuestion:
Q1. What type of analysis?
- 🔍 Investigation — "Why did this happen?" Root cause analysis, anomaly detection, ad-hoc deep dives.
- 📈 Modeling — "Can we predict/classify/segment?" Statistical modeling, ML, forecasting.
- 🔮 Simulation — "What would happen if we do X?" Policy evaluation, pricing strategy, resource allocation.
(These are available as separate commands:)
- 📊 Monitoring →
/monitor setup - 🧪 Experiment →
/experiment new
Step 2b: Ask mode and details
Q2. Analysis mode?
- Full — 5 ALIVE files + full checklists.
- Quick — Single file with abbreviated ALIVE flow.
Q3. Analysis title?
- Free text input
Q4. (Full only) Brief description
- Investigation: "What do you want to find out?"
- Modeling: "What do you want to predict or classify?"
- Simulation: "What policy or strategy are you evaluating?"
- This seeds the ASK phase.
Q5. Tags (optional)
- Suggest tags from config.md's Tags list if available
- Also suggest based on title/description: "Based on your title, relevant tags might be:
retention,mobile" - User can accept suggestions, add custom tags, or skip
- Format: comma-separated, lowercase, no spaces (use hyphens for multi-word:
user-onboarding)
Step 2c: Quick→Full succession
- Read the Quick file referenced by
--from {ID} - Extract content from each ALIVE section
- Use as seed content for Full analysis files using the mapping below
- Add a reference link in the Quick file:
> ⬆️ Promoted to Full: {new Full ID}
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.
- 4d ago First seen · 848 lines · 0 tokens per session scan A fc748836d22f
analysis-new 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 6,506 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
help
아래 레퍼런스 카드를 사용자에게 그대로 보여주고, 상황에 맞는 다음 한 걸음을 한 줄로 추천하세요 (.oculpm/ 이 없으면 /oculpm:projectinit, 활성 플랜이 있으면 /oculpm:next).
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.
inception
새 프로젝트/기능 영역의 설계 시작 — 리서치→사양 확정→3-depth 계획→EVALS→rules 시드.
next
활성 플랜의 다음 미완 리프를 잡아 구현 — 구현→검증→일지→플랜 갱신 한 사이클.
standup
ocul-pm 추적 프로젝트의 오늘 작업 스탠드업 — 일지·플랜 진행을 모아 요약 보고.
generate-extension
Create Shopify app extension (Functions, Theme App Extension, or Admin UI) with proper scaffolding and configuration.