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/blackzhanzhan/cyber-ming-protocol/cursor-startergit clone --depth 1 https://github.com/blackzhanzhan/Cyber-Ming-ProtocolWrote 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/blackzhanzhan/cyber-ming-protocol/cursor-starter)<a href="https://agentmods.dev/rules/blackzhanzhan/cyber-ming-protocol/cursor-starter"><img src="https://agentmods.dev/badge/rules/blackzhanzhan/cyber-ming-protocol/cursor-starter.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 | $0.00421 | $0.00421 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
cursor-starter 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 4d 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
Cyber-Ming Starter
This workspace uses Cyber-Ming-Protocol.
- Bootstrap under repository law before editing.
- Default to contract development before code changes.
- Route planning through
contract-hook-routerwhen the skill is available. - Enter
free development mode/自由开发模式only when the user explicitly activates it. - Keep Cyber-Ming's sovereign/imperial narrative available as style, while keeping operational instructions readable in the user's language.
- If
dev_repo/state.json,journal.jsonl,evidence_index.json, ortree.mdexist, treat them as current runtime truth. - If
dev_repo/architecture/exists, treat it as current architecture truth before planning broad changes. - If
dev_repo/architecture/data-model/exists, treat it as current data-model truth before planning durable data, schema, migration, or persistence changes. - In fresh or takeover sessions, reconstruct state and initialize/read architecture truth before edits.
- Treat host plan/ask modes as
plan-starthook surfaces only. Compile plans into Cyber-Ming contracts before execution. - If a change alters architecture boundaries, responsibilities, dependencies, runtime flows, or invariants, use an architecture amendment contract rather than a normal implementation contract.
- If a change alters entities, relationships, identity, cardinality, source/derived status, migrations, backfills, or persistence semantics, use an ER/data-model amendment contract rather than a normal implementation contract.
Recommended first prompt:
{{FIRST_PROMPT}}
Reference docs live at:
{{DOCS_ROOT}}/BOOTSTRAP.md{{DOCS_ROOT}}/bootstrap/ide-executor.md{{DOCS_ROOT}}/bootstrap/web-auditor.md{{DOCS_ROOT}}/dev_repo-runtime.md{{DOCS_ROOT}}/architecture/README.md{{DOCS_ROOT}}/architecture/data-model/README.md
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.
- 4d ago First seen · 38 lines · 421 tokens per session scan A 4134311209c8
cursor-starter is a cursor rule published in the GitHub repository blackzhanzhan/Cyber-Ming-Protocol (56 stars, last pushed 3mo ago), licensed MIT. It adds 421 tokens to every session, about $0.0021 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
meta-theory-dispatch
Meta-theory dispatch entry and deep Fetch requirement for Cursor.
meta-enforcement
Meta-agent execution boundary enforcement — meta- agents must not perform direct execution work in Cursor.
meta-choice-surface
MetaKim choice-surface fallback — stable Cursor trigger for blocking user decisions.
main
Cursor rule "main" from Bita71/Agent-Workflow-Kit, covering cursor adapter, commands and roles.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
swift
Swift patterns: SwiftUI, actors, async/await, value types.