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-listgit 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-list)<a href="https://agentmods.dev/commands/with-geun/alive-analysis/analysis-list"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-list.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.00645 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
analysis-list 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analysis list
List all analyses (active + archived).
Instructions
Step 1: Scan active analyses
Read all files/folders in analyses/active/:
- Full analyses: folders matching
F-* - Quick analyses: files matching
quick_Q-*
Step 2: Scan archived analyses
Read all year-month folders in analyses/archive/:
- List each analysis with its summary (if summary.md exists)
Step 3: Display full list
Format output grouped by status:
═══════════════════════════════════════════════════
alive-analysis — All Analyses
═══════════════════════════════════════════════════
🟡 Active (2)
─────────────
F-2026-0210-001 DAU drop investigation 🔍 INVESTIGATE [retention, mobile]
Q-2026-0210-002 Retention check 📢 VOICE [retention, onboarding]
✅ Archived — 2026-02 (3)
──────────────────────────
F-2026-0208-001 Payment funnel analysis → "Desktop 2x higher conversion"
Q-2026-0207-001 Sign-up conversion rate → "Mobile 30% lower"
F-2026-0205-002 Churn root cause → "Day-7 drop correlates with onboarding skip"
✅ Archived — 2026-01 (1)
──────────────────────────
F-2026-0128-001 Q4 revenue deep dive → "APAC grew 40% YoY"
Total: 6 analyses (2 active, 4 archived)
═══════════════════════════════════════════════════
Step 4: Optional filters
If the user provides arguments:
/analysis list --active→ show only active/analysis list --archived→ show only archived/analysis list --month 2026-02→ filter by month/analysis list --search {keyword}→ search titles and insights/analysis list --tag {tag}→ filter by tag (e.g.,--tag retention)/analysis list --related {ID}→ show analyses with overlapping tags to {ID}
Step 5: Quick actions
After displaying the list, suggest:
- For active analyses: "Use
/analysis nextto advance,/analysis archiveto complete" - For archived analyses: "Archived analyses are in
analyses/archive/{month}/" - If
--related {ID}used: show related analyses and suggest: "These analyses share tags with {ID}. Review them for reusable insights or methods."
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 · 69 lines · 0 tokens per session scan A 16bc96238882
analysis-list 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 645 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.