/mole-explore

A command for creating or continuing an OpenMole change while scanning code for bad smells, such as patterns that may make code harder to maintain. OpenMole changes are tracked work items stored in an openmole/changes/ folder.

In plain words
What is it for?
Use it to scan a chosen path, name a change, and write the discovered bad smells to openmole/changes/<change>/badsmells.md.
Why use it?
It gives a repeatable place to record a refactoring or other code change and the problems found during exploration. This avoids losing the findings in an informal code review or chat.

Command 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 commands/agiledon/openmole/mole-explore
Clone the repo
git clone --depth 1 https://github.com/agiledon/openmole

Made for: Cursor.

Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 113 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.00031 $0.00113
Opus 5 $0.00015 $0.00056
Sonnet 5 $0.00006 $0.00023
Haiku 4.5 $0.00003 $0.00011

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

Security

Grade A, and why

/mole-explore 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/commands/mole-explore.md · 12 lines

What it actually says

Load and follow the openmole-explore skill.

参数:[path] 扫描范围(默认 .);[change-name] kebab-case 变更名(可选)。

示例:mole:explore src/auth refactor-auth-module

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 · 12 lines · 31 tokens per session scan A 90f2cb213b96

Subscribe to this mod's changes

/mole-explore is a command published in the GitHub repository agiledon/openmole (23 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 113 once invoked, about $0.0002 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.