030-wave-execution Cursor ruleA
030-wave-execution from kanevry/session-orchestrator is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add kanevry/session-orchestrator/.cursor/rules/030-wave-execution.mdc@git:20260825.0626387Pins git:20260825.0626387 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- kanevry/session-orchestrator
- Path
.cursor/rules/030-wave-execution.mdc- Versions recorded
- 5
- Latest version
- git:20260825.0626387, committed Aug 25, 2026
- First version recorded
- Apr 7, 2026
- Size
- 11,256 bytes
- Repository stars
- 53
- License
- MIT
When executing session plan waves via /go command — task sequencing, quality checks, progress tracking.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Wave Execution (Cursor Adaptation) > **CRITICAL**: Cursor does NOT have an `Agent()` tool. All wave tasks execute **sequentially in the current Composer session**. You are both the coordinator AND the implementer. Agent dispatch (3-tier resolution: project > plugin > general-purpose) is NOT applicable — follow the role's agent-prompt patterns directly. > **State directory**: All state files live in `.cursor/` (STATE.md, wave-scope.json). ## Pre-Execution Before starting Wave 1: 1. `git status --short` — commit or stash any uncommitted changes 2. Capture baseline: `SESSION_START_REF=$(git rev-parse HEAD)` — keep for the whole session 3. Confirm the agreed plan is still valid 4. Read `persistence` from Session Config (default: `true`) ### Initialize STATE.md (if persistence enabled) Create `.cursor/STATE.md` (`mkdir -p .cursor` if needed): ```yaml --- schema-version: 1 session-type: feature|deep|housekeeping branch: <current branch> issues: [<issue numbers from plan>] started_at: <ISO 8601 timestamp> status: active current-wave: 0 total-waves: <from session plan> --- ``` ```markdown ## Current Wave Wave 0 — Initializing ## Wave History (none yet) ## Deviations …
Read the whole file at its exact version.
How to install
mdr add kanevry/session-orchestrator/.cursor/rules/030-wave-execution.mdc@sha256:20309cb5c882a059The line at the top of this page pins the label git:20260825.0626387, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5wzwdx5jh4scche4)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 7, 2026 and Aug 25, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260825.0626387 latest | 2026-08-25 | 0626387 | 11,256 B | A | view · diff |
| git:20260814.fd73548 | 2026-08-14 | fd73548 | 11,174 B | A | view · diff |
| git:20260803.fdc7731 | 2026-08-03 | fdc7731 | 9,144 B | A | view · diff |
| git:20260407.1cd1ead | 2026-04-07 | 1cd1ead | 7,474 B | A | view · diff |
| git:20260407.0d7ba8f | 2026-04-07 | 0d7ba8f | 7,672 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (11256 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kanevry/session-orchestrator · 53 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5wzwdx5jh4scche4 GET https://markdownregistry.com/api/v1/resolve?ref=kanevry/session-orchestrator/.cursor/rules/030-wave-execution.mdc GET https://markdownregistry.com/api/v1/blob/20309cb5c882a0594f15248688c87099ebbc1ac1f9fcc81f973c1f58619d3d3a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.