cursor-session-init

A Cursor session startup rule for projects using the loom workflow. It checks project guidance, memory, available skills, and unfinished specification-based work before responding to a request.

In plain words
What is it for?
It helps check for the .loom directory, read the relevant project context, load only needed skill information, and report active development tasks.
Why use it?
It prevents work from starting without knowing the repository’s rules, current workflow settings, or unfinished tasks.

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/xiqin/loom/cursor-session-init
Clone the repo
git clone --depth 1 https://github.com/xiqin/loom
Per session 304 This file is loaded in full into every session.
When invoked 304 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.00304 $0.00304
Opus 5 $0.00152 $0.00152
Sonnet 5 $0.00061 $0.00061
Haiku 4.5 $0.00030 $0.00030

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

Security

Grade A, and why

cursor-session-init 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.

templates/cursor-session-init.mdc · 20 lines

What it actually says

loom 会话初始化

每次开始工作前,必须先执行以下检查,再响应用户请求:

  1. 检查 .loom/ 目录是否存在。若不存在,提示用户运行 /loom-init-project,然后停止。
  2. 读取 .loom/workflow.yaml 了解当前项目的流水线配置。
  3. 渐进式加载上下文文件(避免整文件读取挤爆上下文):
    • .loom/rules/constitution.md:先用 loom_get_context(doc="constitution") 取目录,按需取节。
    • .loom/memory/MEMORY.md:先用 loom_get_context(doc="memory") 取目录。
    • .loom/rules/product.md:若存在,仅读取关键章节。
  4. 渐进式加载技能文件:用 loom_get_skill_context() 获取所有技能的 L0 摘要,仅当需要执行某技能时用 loom_get_skill_context(skill="技能名") 获取完整内容。禁止一次加载所有 SKILL.md 全文
  5. 检查 specs/ 目录下是否有进行中的开发任务(有 spec.md 但无 verify-report.md 的目录),若有,列出当前阶段。

完成以上检查后,简要输出状态,然后响应用户请求。

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 · 20 lines · 304 tokens per session scan A d5f73164d575

Subscribe to this mod's changes

cursor-session-init is a cursor rule published in the GitHub repository xiqin/loom (5 stars, last pushed 1mo ago), licensed MIT. It adds 304 tokens to every session, about $0.0015 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.