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-initgit clone --depth 1 https://github.com/with-geun/alive-analysisWhat 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.02308 |
| Opus 5 | $0.00000 | $0.01154 |
| Sonnet 5 | $0.00000 | $0.00462 |
| Haiku 4.5 | $0.00000 | $0.00231 |
Grade A, and why
analysis-init 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 2d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analysis init
Initialize alive-analysis in the current project.
Instructions
You are setting up the alive-analysis workflow kit for this project. This is the most important step — the context collected here will be used throughout every analysis to make conversations smarter and faster.
All questions are optional — the user can skip anything they don't know yet. Follow these steps in order:
Quick Setup Mode
For a quick setup, run
/analysis init --quick. For full configuration, continue below.
If the user ran /analysis init --quick:
- Ask only 3 questions:
- Language (default: English)
- Team/project name
- Default mode (default: Quick)
- Skip Steps 3-6 (goals, metrics, stakeholders, data stack) entirely
- Jump directly to Step 8 (Create folder structure)
- Generate config.md with empty sections and a comment: "Fill these in later with
/analysis init --update" - Proceed to Step 10 and Step 11 as normal
Step 1: Check existing setup
Tip: For a quick setup with minimal questions, run
/analysis init --quick.
Check if .analysis/ folder already exists.
- If it exists, warn the user and ask if they want to re-initialize.
- If not, check if the
--quickflag was provided.
If --quick flag detected:
- Ask only 3 questions:
- Q1. Language — "What language for analysis documents?" (default: English)
- Q2. Team/project name — Free text
- Q3. Default analysis mode — Full or Quick (default: Quick)
- Skip Steps 3-6 entirely (goals, metrics, stakeholders, data stack)
- Jump to Step 8 (Create folder structure)
- In Step 9, generate config.md with all skipped sections showing:
> Not configured yet — run `/analysis init --update` to fill in. - Continue to Steps 10-11 as normal
If no flag (full setup): Continue to Step 2 below.
Step 2: Language (ask first)
Ask the user what language they want for analysis documents. Accept any natural language input — don't limit to a dropdown.
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.
- 2d ago First seen · 283 lines · 0 tokens per session scan A d49987c09c1d
analysis-init 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 2,308 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.