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/experiment-archive)<a href="https://agentmods.dev/commands/with-geun/alive-analysis/experiment-archive"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/experiment-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.1 | $0.00000 | $0.00704 |
| Opus 5 | $0.00000 | $0.00352 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
experiment-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 7d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/experiment archive
Archive a completed experiment.
Instructions
Step 1: Identify experiment to archive
Read .analysis/status.md for active experiments (Type: 🧪 Experiment).
- If argument provided (ID), use that
- If only 1 active experiment in LEARN stage → select automatically
- Otherwise, show list and ask user which to archive
- Warn if the experiment hasn't reached DECIDE stage yet: "This experiment is still in {stage}. Archive anyway? (Archiving early is OK for cancelled/abandoned experiments)"
Step 2: Generate summary.md
For Full Experiment:
Read all stage files (01_design.md through 05_learn.md) and generate:
# Summary: {title}
> ID: {ID}
> Period: {start_date} ~ {end_date}
> Type: 🧪 Experiment | Owner: {owner}
## Outcome
- **Hypothesis**: {from 01_design.md}
- **Result**: Confirmed / Rejected / Inconclusive
- **Decision**: 🚀 Launched / 🔴 Killed / ⏳ Extended / 🔄 Iterated
## Key Numbers
| Metric | Control | Treatment | Δ | Significant? |
|--------|---------|-----------|---|-------------|
| {primary} | | | | |
## Key Takeaway
- (Extract from 05_learn.md "One-Sentence Takeaway", or ask user)
## Impact
- (Extract from 04_decide.md impact estimate)
## Follow-Up
- Experiments: (from 05_learn.md)
- Analyses: (from 05_learn.md)
- Monitoring: (post-launch checkpoints status)
## Reproduction
- Key assets: `assets/`
- Design doc: `01_design.md`
For Quick Experiment:
Generate a compact summary appended to the Quick file header:
> ✅ Archived: {today} | Result: {decision} | Takeaway: {one-line summary}
Step 3: Move to archive
Determine archive folder: ab-tests/archive/{YYYY-MM}/
- Create the year-month folder if it doesn't exist
- Move the full experiment folder (or quick file) from
active/toarchive/{YYYY-MM}/ - For Full: place
summary.mdinside the experiment folder
Step 4: Update status.md
- Remove the experiment from the "Active" table
- Add to "Recently Archived" table (keep max 5 entries, remove oldest)
- Update counts and "Last updated" timestamp
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.
- 7d ago First seen · 94 lines · 0 tokens per session scan A 474a3db274cf
experiment-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 704 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
read
Accepts: local PDF path, DOI, journal URL, or a pasted abstract with basic metadata.
project_init
A command that starts tracking a project with ocul-pm by creating its project records and agent logging rules.
protocol
Generate a bioprotocol using Elnora AI.
graphql
Build version-safe Shopify Admin GraphQL queries and mutations, optimize query cost, and implement error handling.
optimize-listing
Optimize Shopify App Store listing for search discovery, conversion, and Built for Shopify certification requirements.
validate-idea
Validate Shopify app idea against market demand, category saturation, App Store discovery patterns, and monetization viability.