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/Kanevry/session-orchestratorWrote 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/kanevry/session-orchestrator/050-plan)<a href="https://agentmods.dev/rules/kanevry/session-orchestrator/050-plan"><img src="https://agentmods.dev/badge/rules/kanevry/session-orchestrator/050-plan/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/kanevry/session-orchestrator/050-plan"><img src="https://agentmods.dev/badge/rules/kanevry/session-orchestrator/050-plan.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.00020 | $0.02346 |
| Opus 5.5 | $0.00008 | $0.00938 |
| Sonnet 5.5 | $0.00004 | $0.00469 |
| Haiku 4.5 | $0.00002 | $0.00235 |
Grade A, and why
050-plan 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 yesterday.
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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan — Structured Project Planning & PRD Generation
Three planning modes with a shared research-driven Q&A engine. Pattern across all modes: research → questions → document → review → issues.
Phase 0: Read Session Config
Read Session Config from CLAUDE.md. plan-baseline-path is required only by /plan new; feature and retro run without it. If /plan new finds it missing or absent, stop with error:
"Error:
plan-baseline-pathis not configured in Session Config. Add it to your CLAUDE.md under## Session Config. Example:plan-baseline-path: ~/Projects/projects-baseline"
Additional fields: plan-default-visibility, plan-prd-location, plan-retro-location, vcs. Expand ~ in paths.
Phase 1: Mode Selection
Parse the argument to determine mode:
new— Project kickoff: scaffolding, architecture decisions, initial setupfeature— Feature PRD: requirements gathering, compact scope, acceptance criteriaretro— Retrospective: data-driven analysis of recent work, learnings extraction
If no mode specified, ask via numbered list:
Which planning mode?
1. new (Recommended) — Project kickoff: full PRD, repo setup, issue creation. Fits a repo that has no PRD yet.
2. feature — One feature: compact scope, acceptance criteria, issues. Cheaper, but assumes the project context already exists.
3. retro — Retrospective on finished work: metrics, reflection, improvement actions. Defines no new scope.
Phase 2: Q&A Engine (Shared Core)
Every question wave follows the same pattern. This is the core mechanic across all modes.
2.1 Pre-Question Research
Before each Q&A wave, perform research sequentially — Cursor has no parallel agents:
- Market/online context — Search for relevant market data, best practices, competitor analysis, or technical patterns for the upcoming questions
- Baseline analysis — Read projects-baseline templates, rules, and scripts at
$BASELINE_PATH(Glob, Grep, Read). Skip it whenplan-baseline-pathis unset (only/plan newrequires it). - Repo context — Analyze current repository for patterns, file structure, dependencies, conventions (skip for
/plan newwave 1)
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.
- yesterday Changed f71b03246760
- 1mo ago Changed cf672170403c
- 1mo ago First seen · 236 lines · 20 tokens per session scan A 5d7a1300df6f
050-plan is a cursor rule published in the GitHub repository Kanevry/session-orchestrator (52 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 2,346 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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .