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-archivegit 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-archive)<a href="https://agentmods.dev/commands/with-geun/alive-analysis/analysis-archive"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-archive.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.00716 |
| Opus 5 | $0.00000 | $0.00358 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
analysis-archive 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 5d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analysis archive
Archive a completed analysis.
Instructions
Step 1: Identify analysis to archive
Read .analysis/status.md for active analyses.
- If argument provided (ID), use that
- If only 1 active analysis in EVOLVE stage → select automatically
- Otherwise, show list and ask user which to archive
- Warn if the analysis hasn't reached VOICE stage yet: "This analysis is still in {stage}. Archive anyway? (Archiving early is OK for cancelled/abandoned analyses)"
- Check Impact Tracking status in the EVOLVE file (or Quick EVOLVE section):
- If empty or all "Pending": warn before proceeding: "Impact Tracking hasn't been filled yet for {n} recommendations. Want to update it before archiving, or archive now with a reminder to revisit in 2-4 weeks?"
- This is advisory, not blocking — proceed if user chooses to archive
Step 2: Generate summary.md
For Full Analysis:
Read all stage files (01_ask.md through 05_evolve.md) and generate:
# Summary: {title}
> ID: {ID}
> Period: {start_date} ~ {today}
> Mode: Full | Owner: {owner}
## Key Insight
- (Extract from 05_evolve.md "One-Sentence Insight", or ask user)
## Key Findings
- (Extract top findings from 03_investigate.md)
- (Extract top findings from 03_investigate.md)
## Decision Impact
- (Extract from 04_voice.md recommendations AND 05_evolve.md Impact Tracking table)
- Decision status: {Accepted / Rejected / Modified / Pending}
- Outcome: {what happened — extract from Impact Tracking if filled}
## Follow-up Analyses
- (Extract from 05_evolve.md proposals)
## Reproduction
- Key assets: `assets/`
- (Extract from 03_investigate.md reproducibility section)
For Quick Analysis:
Generate a compact summary appended to the Quick file header:
> ✅ Archived: {today} | Insight: {one-line summary}
Step 3: Move to archive
Determine archive folder: analyses/archive/{YYYY-MM}/
- Create the year-month folder if it doesn't exist
- Move the full analysis folder (or quick file) from
active/toarchive/{YYYY-MM}/ - For Full: place
summary.mdinside the analysis folder
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.
- 5d ago First seen · 90 lines · 0 tokens per session scan A 07a2b2475315
analysis-archive 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 716 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.
learn
Learn about Task Master capabilities through interactive exploration.
start-13-5.es
Bienvenido a Lección 13-5: Despliegue en Vercel.
start-13-5
Command "start-13-5" from minicoohei/ai-agent-camp, covering 🎓 lesson 13-5: vercelデプロイ, 📍 このセッションでやること, 🎯 準備チェック, 🔍 step 0: プロジェクト存在チェック and output/lp-project ディレクトリの存在チェック.
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.
standup
ocul-pm 추적 프로젝트의 오늘 작업 스탠드업 — 일지·플랜 진행을 모아 요약 보고.