core-entry

A short Chinese-language execution protocol that applies to every conversation in a project.

In plain words
What is it for?
Use it to define project-wide working rules, acceptance checks, output requirements, and whether reports or change logs must be updated.
Why use it?
It sets shared expectations for language, concise actionable output, tool use, and the minimum checks needed before a task is considered finished.

Cursor rule

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 rules/mikonos/cursor-skill-infra/core-entry
Clone the repo
git clone --depth 1 https://github.com/mikonos/cursor-skill-infra
Per session 183 This file is loaded in full into every session.
When invoked 183 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00183 $0.00183
Opus 5 $0.00092 $0.00092
Sonnet 5 $0.00037 $0.00037
Haiku 4.5 $0.00018 $0.00018

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

Security

Grade A, and why

core-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 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/rules/core-entry.mdc · 21 lines

What it actually says

Core Entry(必经协议)

这是一个“每次都注入”的最小执行协议模板。请按你的项目需要修改/删减。

默认工作方式

  • 语言:中文(或按项目约定)
  • 输出:可执行 + 可验收(少废话)
  • 工具:优先用 IDE/内置工具,能确定性执行就不要靠“脑补”

任务结束时的最小验收(示例)

  • 你可以把这里替换成你的质量门槛,例如:
    • 检查清单
    • 产出格式契约
    • 是否更新周报/变更日志(如果你的系统需要)
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 · 21 lines · 183 tokens per session scan A f1d40b95818e

Subscribe to this mod's changes

core-entry is a cursor rule published in the GitHub repository mikonos/cursor-skill-infra (2 stars, last pushed 7mo ago), licensed MIT. It adds 183 tokens to every session, about $0.0009 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.