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-agentgit 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-agent)<a href="https://agentmods.dev/commands/with-geun/alive-analysis/analysis-agent"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-agent.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.01033 |
| Opus 5 | $0.00000 | $0.00517 |
| Sonnet 5 | $0.00000 | $0.00207 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
analysis-agent 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analysis-agent
Run a specialist sub-agent for the current analysis stage.
Usage:
/analysis-agent— show top recommended agents for current stage/analysis-agent 1— run the #1 recommended agent/analysis-agent 1 3— run agents #1 and #3 in parallel/analysis-agent all— run all recommended agents/analysis-agent "통계"— fuzzy match by alias and run
Instructions
Step 1: Load context
- Read
.analysis/status.md→ find active Full analysis (or ask which if multiple) - Read
.analysis/agent-state.md(if exists) → load suppression history - Read
.analysis/agents.yml(if exists, else fallback tocore/config/agents.yml) → user config - Determine current stage from analysis folder (which stage files exist)
- Read the current stage file (all sections)
Step 2: Parse argument
No argument → go to Step 3 (show recommendations)
Number(s) (e.g., 1, 1 3, all) → go to Step 5 (execute directly)
- "all" = run all agents in the last recommendation block
Free text / alias (e.g., "통계", "hypothesis", "리뷰") →
- Fuzzy-match against
id,label, andaliasesfields incore/agents/registry.yml - If 1 match: run it directly → Step 5
- If 2+ matches: show compact list, ask user to pick (single question)
- If 0 matches: show "No match. Available agents for {stage}: {list}" and exit
Step 3: Evaluate router (no-arg flow)
Apply routing rules from core/agents/router.yml for current stage:
- Check gates: evaluate gate auto_run conditions → list auto-run gates separately
- Score optional agents: apply rule conditions + bonuses → filter by min_score_threshold
- Apply suppression: skip agents in agent-state.md for this stage (unless content hash changed)
- Apply user config: skip disabled agents, honor max_recos_per_stage
- Take top_k: select top 3 by score
Step 4: Show recommendation block
─────────────────────────────────────────────────────
🤖 Specialist Recommendations — {STAGE} stage
Analysis: {ID} — {title}
─────────────────────────────────────────────────────
{If auto-gates fired:}
[auto] Running {gate-id} — {reason}
{Recommendations:}
1. {label} — {reason_template from router.yml}
2. {label} — {reason_template}
3. {label} — {reason_template}
─────────────────────────────────────────────────────
Run? (1 / 2 / 3 / 1 3 / all / n) →
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 · 108 lines · 0 tokens per session scan A d25cccf3c32f
analysis-agent 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 1,033 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.