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.
npx agentmods add rules/btspoony/mstar-harness/mstar-entrygit 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-entry)<a href="https://agentmods.dev/rules/btspoony/mstar-harness/mstar-entry"><img src="https://agentmods.dev/badge/rules/btspoony/mstar-harness/mstar-entry.svg" alt="Measured on agentmods" 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.00140 | $0.00140 |
| Opus 5 | $0.00070 | $0.00070 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
mstar-entry 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 6d 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.
What it actually says
When this plugin is active, always load skill mstar-harness-core first (SKILL.md and relevant references/) before non-trivial tasks. Resolve it from the loaded plugin skill root — not as a consumer-project path skills/mstar-harness-core/….
mstar-harness-core is the single source of truth for lifecycle gates, routing, host entry behavior, skill loading order, and execution invariants across all mstar-* skills.
Use this plugin as a Cursor-native entrypoint for Morning Star harness workflows.
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.
- 6d ago First seen · 11 lines · 140 tokens per session scan A 68211d3952d8
mstar-entry is a cursor rule published in the GitHub repository btspoony/mstar-harness (58 stars, last pushed today), licensed MIT. It adds 140 tokens to every session, about $0.0007 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-30.
Other cursor rules, from other repositories
planr-pipeline-ship
Planr Pipeline — DEV Phase orchestration (ship {feature}). Frontend ‖ backend → qa → devops ‖ doc-gen → snapshot → marker.
planr-pipeline-plan
Planr Pipeline — PO Phase orchestration (plan {feature}). Decomposes a spec into User Stories + Tasks. STOPS at the human-review gate.
planr-pipeline
Planr Pipeline orchestration — PO/DEV phase rules, R1 human gate, mode detection, runtime parity for planr-pipeline.
implement-task-list
Implement Task List — context-aware task implementation guide for planr-pipeline.
openplanr-operate
Agent-native OpenPlanr Operating Board workflow for Cursor.
agile-checklist
Agile Development Checklist — guides you through the 5-phase agile workflow for planr-pipeline.