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.
git 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00645 |
| Opus 5.5 | $0.00000 | $0.00258 |
| Sonnet 5.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 1mo 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.
- 1mo 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 4mo 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
project_init
A command that starts tracking a project with ocul-pm by creating its project records and agent logging rules.
standup
A command that creates a daily stand-up report from an ocul-pm project's work logs and plan. A stand-up is a short update on completed work, blocked work, and next steps.
inception
A command for starting the design of a new project or major feature area. It guides research, agreement on the specification, a detailed three-level plan, evaluation checks, and initial project rules.
start-shopify-app
Start a beginner-friendly Shopify app project from idea or an existing repository.
add-webhook
Add a reliable authenticated Shopify event handler and test failure cases.
audit-scopes
Audit Shopify scopes and protected-data access without expanding permissions.