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-learn-nextgit 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-learn-next)<a href="https://agentmods.dev/commands/with-geun/alive-analysis/analysis-learn-next"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-learn-next.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.01129 |
| Opus 5 | $0.00000 | $0.00564 |
| Sonnet 5 | $0.00000 | $0.00226 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
analysis-learn-next 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analysis-learn-next
Review the current stage and advance to the next ALIVE stage in a learning session.
Instructions
Step 1: Identify current learning session
Read .analysis/education/progress.md to find the active learning session (In Progress table).
- If no active session → tell user: "No active learning session. Run
/analysis-learnto start one." - If multiple active sessions → ask which one to advance
- Read the scenario metadata from
core/education/scenarios/{scenario-id}/metadata.md
Step 2: Determine current stage
Beginner (Quick): Read the learning file. Check which sections have been filled in (not just template placeholders):
- ASK filled → current stage is ASK, next is LOOK
- ASK + LOOK filled → current is LOOK, next is INVESTIGATE
- ASK + LOOK + INVESTIGATE filled → current is INVESTIGATE, next is VOICE
- ASK + LOOK + INVESTIGATE + VOICE filled → current is VOICE, next is EVOLVE
- All filled → current is EVOLVE, analysis complete → suggest
/analysis-learn-review
Intermediate (Full): Check which files exist in the learning folder:
- Only
01_ask.md→ current is ASK, next is LOOK - Up to
02_look.md→ current is LOOK, next is INVESTIGATE - Up to
03_investigate.md→ current is INVESTIGATE, next is VOICE - Up to
04_voice.md→ current is VOICE, next is EVOLVE - All 5 files → EVOLVE complete → suggest
/analysis-learn-review
Step 3: Review current stage (feedback)
Read the rubric from core/education/scenarios/{scenario-id}/rubric.md.
Read the solution from core/education/scenarios/{scenario-id}/solution/.
Read the learner's current stage content.
Provide feedback:
- Score the current stage using the rubric criteria (out of the stage's max points)
- What you did well — 2-3 specific things the learner got right
- What you missed — 1-3 things that could be stronger, with explanation of WHY they matter
- Key takeaway — One sentence summarizing the most important lesson from this stage
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 · 107 lines · 0 tokens per session scan A 3f8e619a0092
analysis-learn-next 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,129 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
mentor
Educational mode that explains concepts, teaches patterns, and guides learning. Ideal when learning a new codebase, technology, or programming concept.
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.
inception
새 프로젝트/기능 영역의 설계 시작 — 리서치→사양 확정→3-depth 계획→EVALS→rules 시드.
standup
ocul-pm 추적 프로젝트의 오늘 작업 스탠드업 — 일지·플랜 진행을 모아 요약 보고.
setup-elevenlabs
Command "setup-elevenlabs" from minicoohei/ai-agent-camp, covering elevenlabs api セットアップ, step 0: セットアップ進捗の確認, このセッションでやること, 準備チェック and step 1: ブラウザでelevenlabsを開く.
setup-clasp.es
Command "setup-clasp.es" from minicoohei/ai-agent-camp, covering configuración de google apps script cli (clasp), step 0: verificar el progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: verificar node.js.