module_executor

A set of rules for loading, running, and monitoring software modules. A module is a self-contained part of a program that may depend on other modules.

In plain words
What is it for?
Use it when designing or operating module loading, dependency resolution, caching, lazy loading, concurrency controls, performance monitoring, and audit logging.
Why use it?
It requires dependencies and initialization to be checked before execution, errors to be handled, and resource use and logs to be monitored. This helps prevent unsafe or unreliable module runs.

Cursor rule for Cursor

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/wangqiqi/cursor-ai-rules/module_executor
Clone the repo
git clone --depth 1 https://github.com/wangqiqi/cursor-ai-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,002 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.02002
Opus 5 $0.00000 $0.01001
Sonnet 5 $0.00000 $0.00400
Haiku 4.5 $0.00000 $0.00200

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

Security

Grade A, and why

module_executor 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/system/module_executor.mdc · 310 lines

How it starts

The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🚀 模块执行器和监控器 (Module Executor & Monitor)

本文档是从 @module_manager 分割出来的执行和监控部分。

⚠️ 执行原则

MUST 遵循以下模块执行准则:

  • MUST 在执行前验证所有依赖项
  • NEVER 跳过模块初始化检查
  • ALWAYS 监控执行性能和资源使用
  • DO NOT 在未处理错误的情况下继续执行
  • MUST 确保线程安全和并发控制
  • ALWAYS 记录执行日志用于审计

加载策略 (Loading Strategies)

即时加载 (Immediate Loading)
class ImmediateLoader implements ModuleLoader {
  async load(moduleName: string): Promise<ModuleInstance> {
    const module = await this.registry.get(moduleName);
    if (!module) {
      throw new Error(`Module ${moduleName} not found`);
    }

    // 检查缓存
    const cached = this.cache.get(moduleName);
    if (cached && this.isCacheValid(cached, module)) {
      return cached.instance;
    }

    // 解析依赖
    const resolution = await this.resolver.resolve(moduleName);

    // 按顺序加载依赖
    for (const depName of resolution.loadOrder) {
      if (depName !== moduleName) {
        await this.load(depName);
      }
    }

    // 加载主模块
    const instance = await this.loadModuleInstance(module);

    // 缓存实例
    this.cache.set(moduleName, {
      instance,
      timestamp: Date.now(),
      metadata: module.metadata
    });

    return instance;
  }
}
懒加载 (Lazy Loading)
class LazyLoader implements ModuleLoader {
  private loadingPromises: Map<string, Promise<ModuleInstance>> = new Map();

  async load(moduleName: string): Promise<ModuleInstance> {
    if (this.loadingPromises.has(moduleName)) {
      return this.loadingPromises.get(moduleName)!;
    }

    const loadPromise = this.performLazyLoad(moduleName);
    this.loadingPromises.set(moduleName, loadPromise);

    return loadPromise;
  }

  private async performLazyLoad(moduleName: string): Promise<ModuleInstance> {
    // 延迟加载逻辑
    await this.delay(100); // 模拟网络延迟或其他准备时间

    const module = await this.registry.get(moduleName);
    if (!module) {
      throw new Error(`Module ${moduleName} not found`);
    }

    return this.loadModuleInstance(module);
  }
}

Read the full file on GitHub · 310 lines

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 · 310 lines · 0 tokens per session scan A 5ba73ee0da46

Subscribe to this mod's changes

module_executor is a cursor rule published in the GitHub repository wangqiqi/cursor-ai-rules (15 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,002 tokens. 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.