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 skills add wpsnote/wpsnote-skills --skill ie-connect-dotsgit clone --depth 1 https://github.com/wpsnote/wpsnote-skillsWrote 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/wpsnote/wpsnote-skills/ie-connect-dots)<a href="https://agentmods.dev/skills/wpsnote/wpsnote-skills/ie-connect-dots"><img src="https://agentmods.dev/badge/skills/wpsnote/wpsnote-skills/ie-connect-dots/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wpsnote/wpsnote-skills/ie-connect-dots"><img src="https://agentmods.dev/badge/skills/wpsnote/wpsnote-skills/ie-connect-dots.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00120 | $0.01610 |
| Opus 5.5 | $0.00048 | $0.00644 |
| Sonnet 5.5 | $0.00024 | $0.00322 |
| Haiku 4.5 | $0.00012 | $0.00161 |
Grade A, and why
ie-connect-dots 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 1mo 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
推理层：想法连接与模式发现
本技能负责分析多条笔记或想法之间的关系，发现隐含连接和长期模式。 这是灵感引擎（Inspiration Engine）三层架构中的中间层，接收记忆层的检索结果，为洞见层提供结构化的推理产物。
适用场景
当需要理解多条笔记或想法之间的关系时使用，典型场景包括：
- 用户给出多条笔记，想知道它们之间有什么联系
- 被 ie-engine 编排器调用，处理 ie-retrieve-memory 的检索结果
- 用户想发现自己长期关注的主题模式
- 用户想对一组零散的想法进行分类整理
不适用场景
以下场景不应使用此技能（避免误触发）：
- 检索或搜索笔记（使用 ie-retrieve-memory）
- 生成洞见文本或探索建议（使用 ie-generate-insight）
- 单条笔记的内容分析或摘要（直接完成即可）
- 通用的数据分析或统计（使用其他合适的工具）
三种推理能力
能力一：语义聚类
将多条笔记或想法按语义相似性分组。
分析方法：
- 提取每条笔记的核心主题和关键概念
- 根据主题相似性将笔记分成若干组
- 为每个组命名，概括组内笔记的共同主题
- 标注组间的远近关系
输出格式：
语义聚类结果
---
聚类 A：[聚类名称]
核心主题：[一句话描述]
包含笔记：
- [笔记标题1]：[与聚类主题的关联点]
- [笔记标题2]：[与聚类主题的关联点]
聚类 B：[聚类名称]
核心主题：[一句话描述]
包含笔记：
- [笔记标题3]：[与聚类主题的关联点]
聚类间关系：
聚类A 与 聚类B：[关系描述，例如"A是B的技术基础"]
能力二：连接假设
提出不同想法之间可能存在的连接，这是灵感引擎最核心的推理能力。
分析方法：
- 识别来自不同聚类或不同时间段的想法
- 寻找它们之间的潜在关联（共同概念、互补性、因果关系、演化关系）
- 为每个连接假设给出置信度和推理依据
- 优先发现那些"不明显但有潜力"的连接
连接类型参考：
- 互补型：两个想法可以组合在一起，形成更完整的方案
- 演化型：一个想法是另一个想法的自然延伸或升级
- 因果型：一个想法的结论可能是另一个想法的前提
- 类比型：两个不同领域的想法有类似的结构或模式
- 冲突型：两个想法存在矛盾，需要调和或选择
输出格式：
连接假设
---
假设 1：[简短标题]
连接类型：[互补型/演化型/因果型/类比型/冲突型]
想法 A：[笔记标题或想法描述]
想法 B：[笔记标题或想法描述]
连接推理：[为什么认为这两个想法有关联，2-3句话]
置信度：高/中/低
潜在价值：[如果这个连接成立，可能带来什么]
假设 2：[简短标题]
...
能力三：长期模式识别
从时间跨度较长的笔记中识别反复出现的主题和关注趋势。
分析方法：
- 按时间线排列笔记
- 标注每条笔记的核心主题
- 识别跨越多个时间段反复出现的主题
- 分析主题的演变趋势（增强、减弱、转向）
输出格式：
长期模式
---
模式 1：[主题名称]
出现频率：在 [时间范围] 中出现 [次数] 次
演变趋势：[增强/减弱/稳定/转向]
代表笔记：
- [时间] [笔记标题]
- [时间] [笔记标题]
趋势解读：[一句话解读这个模式意味着什么]
模式 2：[主题名称]
...
输入要求
本技能接受以下任一形式的输入：
- ie-retrieve-memory 的检索结果（推荐，流水线标准路径）
- 包含笔记标题、ID、标签和内容摘要
- 用户直接提供的笔记内容或想法列表
- 至少需要 2 条以上的笔记或想法才能进行关系分析
- 笔记 ID 列表
- 需要先读取笔记内容再进行分析
如果输入内容不足 2 条，提示用户提供更多素材或先使用 ie-retrieve-memory 检索。
输出综合结构
当三种能力同时使用时，按以下结构组织完整输出。这个格式设计为可以直接传递给洞见层（ie-generate-insight）使用。
推理分析结果
===
一、语义聚类
[聚类结果]
二、连接假设
[连接假设列表，按置信度排序]
三、长期模式
[模式识别结果]
---
分析置信度：高/中/低
输入笔记数量：[数量]
分析覆盖时间范围：[起止时间]
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.
- 1mo ago First seen · 181 lines · 120 tokens per session scan A b8663ec15a69
ie-connect-dots is a skill published in the GitHub repository wpsnote/wpsnote-skills (183 stars, last pushed today), licensed MIT. It adds 120 tokens to every session and 1,610 once invoked, about $0.0005 per session on Opus 5.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
causal-memory
Causal memory for agents — install/setup the causal-memory MCP server, then record decisions/outcomes and recall them before acting. Trigger when the user asks to install or set up causal-memory/agent memory, when causal-memory MCP tools are available and the agent faces a non-trivial decision (architecture, debugging…
remem
Use when the user asks Codex to recall prior project context, save durable decisions or bug fixes, inspect remem memory health, or activate remem automatic memory hooks from the Codex plugin.
evo-memory-review
Review and curate an evo-subagent role's prefercmd.md and memory.md using evidence from actual runs. Use when evolution entries are stale, duplicated, contradictory, or too noisy.
ai-memory-coding-conventions
Project coding conventions extracted from chat history. Load when writing new code, naming things, designing APIs, or reviewing PRs. Topics: Cursor pagination is mandatory for all paged GraphQL endpoints.
ai-memory-decision-log
Technical decisions made for this project, with reasoning and rejected alternatives. Load when proposing architectural changes, evaluating alternatives, or asked why a choice was made. Topics: Adopt OAuth 2.0 authorization code flow with PKCE for the customer portal SPA.
ai-memory-system-architecture
System architecture facts: components, data flow, integration boundaries. Load when implementing cross-component features, debugging integration issues, or onboarding to the codebase. Topics: Event sourcing for the billing audit log.