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-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/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-agent"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-agent.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.01033 |
| Opus 5.5 | $0.00000 | $0.00413 |
| Sonnet 5.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 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 — 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.
- 1mo 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 4mo 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
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.