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 skills/agiledon/openmole/openmole-explorenpx skills add agiledon/openmole --skill openmole-exploregit clone --depth 1 https://github.com/agiledon/openmoleWrote 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/skills/agiledon/openmole/openmole-explore)<a href="https://agentmods.dev/skills/agiledon/openmole/openmole-explore"><img src="https://agentmods.dev/badge/skills/agiledon/openmole/openmole-explore.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.00025 | $0.00986 |
| Opus 5 | $0.00013 | $0.00493 |
| Sonnet 5 | $0.00005 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
openmole-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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenMole Explore — 识别坏味道
路径解析说明:
{cwd}= 用户运行 mole 命令时的当前工作目录{config_dir}= OpenMole 用户级配置目录(~/.config/openmole/)- 完整说明见主版本
skills/openmole-explore/SKILL.md
何时使用
用户运行 mole:explore 或需要识别/更新坏味道清单时。
工作区解析
- 读取
{cwd}/openmole/config.yaml→current_change {change_dir}={cwd}/openmole/changes/{change_name}/- 无
{cwd}/openmole/config.yaml→ 提示从{config_dir}/templates/openmole-config.yaml.example创建
D3 生命周期
| 条件 | 行为 |
|---|---|
无 current_change |
新建 change;名称由 [change-name] 指定或 Agent 提议 + 用户确认 |
有 active change 且未传 [change-name] |
询问:继续当前(升版 badsmells)/ 新建 change |
显式 [change-name] |
目录不存在则创建;存在则在该 change 内升版 |
新建 change 时:
- 创建
{cwd}/openmole/changes/<name>/、{cwd}/openmole/changes/<name>/.openmole-change.yaml(参考{config_dir}/templates/openmole-change.yaml) - 更新
{cwd}/openmole/config.yaml的current_change
跨 change 去重(步骤 0)
- 扫描
{cwd}/openmole/changes/*/badsmells.md与{cwd}/openmole/changes/archive/*/badsmells.md§2.0 - 构建 BS-ID 与指纹
(规范化路径, Fowler 标签) - 已消除同指纹 → 跳过,注明原 change
- 未清除/部分残余于其他 change → 警告,不得静默重复
扫描流程
- 确定范围:
[path]默认. - 检测语言:Python / Java / TypeScript 等
- 识别坏味道:Fowler + §3 原则 + SOLID
- 分配 BS-ID:
BS-<CATEGORY>-<NNN> - 写入
{change_dir}/badsmells.md
输出格式
- 使用
{config_dir}/templates/badsmells-header.md+badsmells-entry.md - §2.0 索引;七字段表格;升版时
git rev-parse HEAD填提交版本
语言附录
Python:pytest、unittest.mock
Java:JUnit、Mockito
TypeScript:jest/vitest
OpenMole 规约摘要(内嵌于各 Skill,非独立文件)
constitution §3 — 八项第一性原则
清晰性、一致性、可读性、复用性、可扩展性、健壮性、安全性、简洁性。
constitution §4 — 标准重构步骤
- 确认坏味道条目
- 确定测试覆盖;无覆盖则先写测试
- 运行测试 → 全绿
- 执行重构(最小 diff,对准 BS-ID)
- 回归测试 → 全绿
- 用户确认(未确认不得标记完成)
constitution §5 — 执行粒度
每次 mole:apply 仅处理一个未完成任务。
specification §4 — badsmells 条目
七字段 + §2.0 状态:未清除 / 已消除 / 部分残余。
specification §7 — 修订历史
升版时 提交版本 = git rev-parse HEAD,未提交填 —。
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 · 95 lines · 25 tokens per session scan A 81e4c86a760b
openmole-explore is a skill published in the GitHub repository agiledon/openmole (23 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 986 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…