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-init)<a href="https://agentmods.dev/commands/with-geun/alive-analysis/analysis-init"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-init/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-init"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/analysis-init.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.02308 |
| Opus 5.5 | $0.00000 | $0.00923 |
| Sonnet 5.5 | $0.00000 | $0.00462 |
| Haiku 4.5 | $0.00000 | $0.00231 |
Grade A, and why
analysis-init 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analysis init
Initialize alive-analysis in the current project.
Instructions
You are setting up the alive-analysis workflow kit for this project. This is the most important step — the context collected here will be used throughout every analysis to make conversations smarter and faster.
All questions are optional — the user can skip anything they don't know yet. Follow these steps in order:
Quick Setup Mode
For a quick setup, run
/analysis init --quick. For full configuration, continue below.
If the user ran /analysis init --quick:
- Ask only 3 questions:
- Language (default: English)
- Team/project name
- Default mode (default: Quick)
- Skip Steps 3-6 (goals, metrics, stakeholders, data stack) entirely
- Jump directly to Step 8 (Create folder structure)
- Generate config.md with empty sections and a comment: "Fill these in later with
/analysis init --update" - Proceed to Step 10 and Step 11 as normal
Step 1: Check existing setup
Tip: For a quick setup with minimal questions, run
/analysis init --quick.
Check if .analysis/ folder already exists.
- If it exists, warn the user and ask if they want to re-initialize.
- If not, check if the
--quickflag was provided.
If --quick flag detected:
- Ask only 3 questions:
- Q1. Language — "What language for analysis documents?" (default: English)
- Q2. Team/project name — Free text
- Q3. Default analysis mode — Full or Quick (default: Quick)
- Skip Steps 3-6 entirely (goals, metrics, stakeholders, data stack)
- Jump to Step 8 (Create folder structure)
- In Step 9, generate config.md with all skipped sections showing:
> Not configured yet — run `/analysis init --update` to fill in. - Continue to Steps 10-11 as normal
If no flag (full setup): Continue to Step 2 below.
Step 2: Language (ask first)
Ask the user what language they want for analysis documents. Accept any natural language input — don't limit to a dropdown.
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 · 283 lines · 0 tokens per session scan A d49987c09c1d
analysis-init 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 2,308 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.