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/btspoony/mstar-harnessWrote 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/btspoony/mstar-harness/mstar-cursor-plan-mode)<a href="https://agentmods.dev/rules/btspoony/mstar-harness/mstar-cursor-plan-mode"><img src="https://agentmods.dev/badge/rules/btspoony/mstar-harness/mstar-cursor-plan-mode/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/btspoony/mstar-harness/mstar-cursor-plan-mode"><img src="https://agentmods.dev/badge/rules/btspoony/mstar-harness/mstar-cursor-plan-mode.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.01038 | $0.01038 |
| Opus 5.5 | $0.00415 | $0.00415 |
| Sonnet 5.5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
mstar-cursor-plan-mode 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morning Star × Cursor Plan mode
When the Morning Star harness plugin or /pm is active and Cursor Plan mode applies (CreatePlan / built-in plan todos):
SSOT vs CreatePlan
- SSOT for plans and status:
{HARNESS_DIR}(default.mstar/, legacy.agents/) —{PLAN_DIR}/<plan-id>-<name>.md,{HARNESS_DIR}/status.json, specs under{SPECS_DIR}when used. - CreatePlan is a session mirror only; do not treat the Cursor plan file URI as the only plan record.
CreatePlan todos (mandatory prefix)
Before any implement/code todo, CreatePlan must list these three bootstrap todos (in order) and complete them on disk:
harness-init— create harness dirs + initializestatus.jsonfrom template when missingspec-register— addplans[]row withplan_idandfilepathmirror-plan— write the SSOT main plan markdown under.mstar/plans/(or resolved{PLAN_DIR})
Implement todo done gate
Do not mark an implement todo complete until:
git commiton the authorized Working branch for that task id (no end-of-plan batch commit unless PM allowed) Each todo's commit uses the configured identity; missing/failing identity is Blocked, never fabricate or use-cidentity overrides →mstar-roles/references/_shared/leaf-executor-core.md§ Git NEVER (repo writes).- matching checkbox
- [x]in the SSOT plan file status.jsonupdated when the coordination round requires it- evidence: real
git log -1 --format='%h %an <%ae>'
Drift and paths
- Keep CreatePlan body and SSOT plan file aligned when scope changes.
- Use SSOT paths in Plan Path / Context Loaded, not only the Cursor plan URI.
mstar-iteration Phase 1 in Plan mode
When Plan mode is used to start a new iteration:
- CreatePlan once as a blank session carrier with pending preparation / Build-bound todos; record its path. The Phase 1 bridge overrides early formal dual-write/bootstrap until the prototype checkpoint passes.
- Feedback loop: update the same session carrier and, when host writes permit, the iteration-package prototype. No formal compass/guides/plans/specs before approval of the presented current prototype. Do not turn feedback into a mandatory questionnaire.
- Feedback-close permits minimal deferred clarification for blocking gaps; it is not design approval. Prototype feedback/revision/re-presentation and restricted-write recovery follow
mstar-host→references/cursor-plan-mode-bridge.md(no alternate tool/child bypass). - Never open a second CreatePlan. Consolidate an accidental duplicate into the original and remove it only when host permissions permit.
- Do not dispatch Review & Edit, commit, or create the integration branch until the user clicks Build.
- Detail:
mstar-host→references/cursor-plan-mode-bridge.md§mstar-iterationPhase 1 in Plan mode.
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.
- 14d ago Changed · +1 lines · +58 tokens per session e81662cd2d65
- 24d ago Changed · +77 tokens per session cb63ec2a1d2b
- 1mo ago First seen · 62 lines · 903 tokens per session scan A fadfd7bc18c8
mstar-cursor-plan-mode is a cursor rule published in the GitHub repository btspoony/mstar-harness (64 stars, last pushed yesterday), licensed MIT. It adds 1,038 tokens to every session, about $0.0042 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
git-commit
A rule applied automatically when creating Git commits. It requires commit messages to omit the Co-authored-by line.
git
Git workflow — commit format, push policy, and PR process.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
git
Cursor rule "git" from duongductrong/cursor-kit, covering git conventions, commit messages, types, subject rules and examples.