060-evolve

060-evolve is a cursor rule for Cursor from Kanevry/session-orchestrator. It costs 20 tokens per session (3,074 once invoked), scanned A, original, MIT.

A learning-management skill for extracting reusable patterns from past sessions and storing or reviewing them when persistence is enabled.

In plain words
What is it for?
Use it to analyze session history, review saved learnings, or choose which new patterns should be stored.
Why use it?
It helps preserve useful lessons between sessions instead of leaving them only in temporary conversation history.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: names the AskUserQuestion tool.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/sweep-expired-learnings.mjs --prune --dry-run --json --entries "$NEXT" --repo-root "$(pwd)".

Good fit Use it to analyze session history, review saved learnings, or choose which new patterns should be stored.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Kanevry/session-orchestrator
agentmods
npx agentmods add rules/kanevry/session-orchestrator/060-evolve

Made for: Cursor.

Wrote 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.

agentmods badge for 060-evolve

README.md
[![agentmods](https://agentmods.dev/badge/rules/kanevry/session-orchestrator/060-evolve/github.svg)](https://agentmods.dev/rules/kanevry/session-orchestrator/060-evolve)
Your own site
<a href="https://agentmods.dev/rules/kanevry/session-orchestrator/060-evolve"><img src="https://agentmods.dev/badge/rules/kanevry/session-orchestrator/060-evolve/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.

agentmods 80×15 button for 060-evolve

Your own site · 80×15
<a href="https://agentmods.dev/rules/kanevry/session-orchestrator/060-evolve"><img src="https://agentmods.dev/badge/rules/kanevry/session-orchestrator/060-evolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,074 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.03074
Opus 5.5 $0.00008 $0.01230
Sonnet 5.5 $0.00004 $0.00615
Haiku 4.5 $0.00002 $0.00307

Measured 15d ago against content hash 88b9818966f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

060-evolve 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 15d 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.

.cursor/rules/060-evolve.mdc · 248 lines

How it starts

The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Evolve — Session Learning Extraction

Extract patterns from session history into reusable learnings. Three modes of operation.

Prerequisites

  • Persistence gate: persistence: true must be set in Session Config. If not, abort: "Learnings require persistence to be enabled in Session Config."
  • Session history must exist at .orchestrator/metrics/sessions.jsonl
  • Learnings are stored at .orchestrator/metrics/learnings.jsonl
  • Config field: learning-expiry-days (default: 30) — legacy window used only by the Review-mode Extend expiry action; new and confirmed learnings derive expires_at per type via deriveExpiresAt() (LEARNING_TTL_DAYS)

Cursor Adaptation

No AskUserQuestion tool on Cursor. Present all choices as numbered Markdown lists:

Which learnings should be saved?

1. [fragile-file] src/lib/auth.ts — Changed in 4 of last 5 sessions (confidence: 0.5 new)
2. [scope-guidance] optimal-scope-per-session-type — 3 issues/session works well (+0.15 update)
3. Skip all — do not save any learnings

Reply with the number(s) of your choice.

Mode Selection

Determine mode from user input (default: analyze):

Mode Purpose
analyze Extract new learnings from session history
review Edit/manage existing learnings interactively
list Display active learnings (read-only)

Mode 1: Analyze

Extract learnings from .orchestrator/metrics/sessions.jsonl.

Step 1: Load Session Data

  1. Read all entries from sessions.jsonl, parse each line as JSON
  2. Sort by completed_at descending (most recent first)
  3. If no sessions found, abort: "No session data available."

Step 2: Pattern Extraction

Apply these heuristics for each learning type:

fragile-file
  • Same file appears in 3+ waves' files_changed within a session, or in 3+ different sessions
  • Subject = relative file path
effective-sizing
  • Compare total_agents and total_waves across session types
  • Calculate average agents per wave per session type
  • Subject = e.g. deep-session-sizing or feature-session-sizing

Read the full file on GitHub · 248 lines

Changes

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.

  1. 15d ago Changed 88b9818966f4
  2. 15d ago Changed · +2 lines ab3198e16cdc
  3. 16d ago Changed · +13 lines 0b5c47ee5f32
  4. 1mo ago First seen · 233 lines · 20 tokens per session scan A 32530add58ab

Subscribe to this mod's changes

060-evolve is a cursor rule published in the GitHub repository Kanevry/session-orchestrator (53 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 3,074 once invoked, about $0.0001 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-08-30.