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 rules/with-geun/alive-analysis/alive-agentsgit 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/rules/with-geun/alive-analysis/alive-agents)<a href="https://agentmods.dev/rules/with-geun/alive-analysis/alive-agents"><img src="https://agentmods.dev/badge/rules/with-geun/alive-analysis/alive-agents.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.00049 | $0.02521 |
| Opus 5 | $0.00024 | $0.01260 |
| Sonnet 5 | $0.00010 | $0.00504 |
| Haiku 4.5 | $0.00005 | $0.00252 |
Grade A, and why
alive-agents 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 4d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
alive-analysis — Sub-agent Dispatch System
This rule activates the Sub-agent Dispatch System on top of the base alive-analysis workflow.
It mirrors the Claude Code behavior using the same core/agents/registry.yml and router.yml.
When this rule applies
Activate when:
- User runs
/analysis-next(stage transition) - User runs
/analysis-agent(explicit specialist call) - User message matches agent aliases: "통계", "가설", "리뷰", "데이터품질", "쿼리", "서술", "윤리", "scope", "sql", "stats", "review", "narrative", "ethics"
Decision Records Check (runs before agent dispatch)
Before evaluating gates or recommendations, check for relevant Decision Records:
- Read
analyses/decisions/INDEX.md(if it exists and has entries) - For each agent about to make a methodology suggestion, check for conflicting DRs:
- hypothesis-gen: check Metric + Scope + Principle DRs
- stats-agent: check Methodology DRs
- metric-definer: check Metric DRs
- If a DR conflicts with a planned suggestion: surface the DR first, do not propose the rejected alternative
- Acknowledge applied DRs with:
> DR-{NNN} 적용: {summary}
Sub-agent Dispatch Protocol
Step 1: Load config
Read .analysis/agents.yml (project-local) or fall back to core/config/agents.yml.
If global.enabled: false → skip all agent dispatch logic.
Step 2: Determine context
- Current stage (from analysis folder: which .md files exist)
- Current stage file content (all sections)
.analysis/agent-state.mdsuppression history (if exists)
Step 3: Evaluate gates
Check gate conditions from core/agents/router.yml:
| Gate | Trigger |
|---|---|
| scope-guard | ASK + Scope empty + Problem Definition filled |
| data-quality-sentinel | LOOK→INVESTIGATE transition + quality incomplete |
| ethics-guard | PII keywords in any content |
| reproducibility-keeper | INVESTIGATE→EVOLVE transition + reproducibility section empty |
For each matching gate (if enabled: true in config):
- Print:
[auto] Running {gate-id} — {reason} - Apply the gate's prompt from
core/agents/prompts/{gate-id}.md - Write output to current stage file
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.
- 4d ago First seen · 222 lines · 49 tokens per session scan A cc5b51d083ee
alive-agents is a cursor rule published in the GitHub repository with-geun/alive-analysis (41 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 2,521 once invoked, about $0.0002 per session on Opus 5. 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 cursor rules, from other repositories
main
Project-wide rules for Cursor agents working on team-telnyx/ai. Loaded by Cursor for every request.
cursorrules
Operating instructions for the Cursor agent working in this repo. This file is the legacy single-file convention. The MDC equivalent lives at .cursor/rules/main.mdc. The canonical source of truth for everything below is AGENTS.md at the repo root — keep these rules in sync with it when changing project-wide guidance.
cursor-rule-snippet
Cursor rule "cursor-rule-snippet" from wufunc/nova, covering memory management, session initialization, explicit remember, reflect and constitution protocol.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.