sandtable-rehearse

A command that runs a sequence of planning exercises: mental rehearsal, opposing review, implementation rehearsal, and retrospective selection. A retrospective is a review of what happened and what should be improved.

In plain words
What is it for?
Use it to rehearse a project, test its plan against attacks, preview implementation, and review the alternatives.
Why use it?
It combines several review stages so plans can be challenged, rehearsed, and refined before choosing an approach.

Command for Cursor

Install

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.

agentmods
npx agentmods add commands/andoop/sandtable/sandtable-rehearse
Clone the repo
git clone --depth 1 https://github.com/andoop/sandtable

Made for: Cursor.

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,372 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00030 $0.01372
Opus 5 $0.00015 $0.00686
Sonnet 5 $0.00006 $0.00274
Haiku 4.5 $0.00003 $0.00137

Measured 2d ago against content hash ebecd8b4ce24, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sandtable-rehearse 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 2d 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/commands/sandtable-rehearse.md · 39 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 39 lines · 30 tokens per session scan A ebecd8b4ce24

Subscribe to this mod's changes

sandtable-rehearse is a command published in the GitHub repository andoop/sandtable (8 stars, last pushed 2mo ago), with no licence file. It adds 30 tokens to every session and 1,372 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-31.