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/FeatureFactory-io/mimirWrote 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/featurefactory-io/mimir/ticket-lifecycle-transitions)<a href="https://agentmods.dev/rules/featurefactory-io/mimir/ticket-lifecycle-transitions"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/ticket-lifecycle-transitions/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/rules/featurefactory-io/mimir/ticket-lifecycle-transitions"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/ticket-lifecycle-transitions.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.00233 | $0.00233 |
| Opus 5.5 | $0.00093 | $0.00093 |
| Sonnet 5.5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
ticket-lifecycle-transitions 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 18d 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.
What it actually says
Rule: Ticket Lifecycle Transitions
Maintain one stable concern per project plus Charter variable_id; update it in place whenever the adapter supports that.
- Green with no open concern: no action.
- Green to Yellow/Orange: open Risk.
- Yellow to/from Orange: keep Risk but update band, severity, evidence, freshness, assessment run, and gating policy.
- Yellow/Orange to Red: reclassify the same concern to Problem.
- Red to Yellow/Orange: reclassify the same concern to Risk and update evidence.
- Fresh non-Green to Green: resolve the concern with recovery evidence.
- Green to Red: open Problem.
- Red to Green: resolve with fresh recovery evidence.
- Any to Unknown: never close or mark Green; create/update the same concern as a measurement-health Risk unless Charter policy is stricter.
- Unknown to measured band: transition that same concern according to the measured band.
Use run_id plus variable_id as the side-effect idempotency key. Retry updates the same ticket/action record. Ticket-adapter failure leaves the assessment incomplete; it never authorizes a duplicate.
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.
- 18d ago First seen · 21 lines · 233 tokens per session scan A e2be77e3a6a1
ticket-lifecycle-transitions is a cursor rule published in the GitHub repository FeatureFactory-io/mimir (16 stars, last pushed 17d ago), licensed Apache-2.0. It adds 233 tokens to every session, about $0.0009 per session on Opus 5.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-09-29.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.