XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Yet, just another hexo plugin for security.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/d0n9x1n-hexo-blog-encrypt)在同一工作中把 AI 连到服务的 MCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
同类工作,排序与 Skill 列表相同
| 本项 hexo-blog-encrypt | MinerU | watermarks-remover | obsidian-skills | anysearch-skill | |
|---|---|---|---|---|---|
| 作者 | D0n9X1n | opendatalab | guillaumemeyer | kepano | anysearch-ai |
| Skill 数 | 1 | 1 | 1 | 5 | 1 |
| GitHub 星标 | 1,051 | 83,972 | 27,796 | 53,183 | 6,906 |
| 最近代码更新 | 2026年10月14日 | 2026年11月18日 | 2026年11月17日 | 2026年9月15日 | 2026年11月13日 |
| 许可证 | MIT | – | MIT | MIT | Apache-2.0 |
D0n9X1n 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
开发者未说明 · SKILL.md 形式的 Skill 可用于支持 Agent Skills 的应用,如 Claude Code、Codex 和 Cursor
GitHub account D0n9X1n (person), 13 years old
★ 1,051 stars · code last changed 2026年10月14日
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 1e1ae52 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (385). Use "Let the AI install it" instead
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /hexo-encrypt-toc,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/d0n9x1n/hexo-blog-encrypt.git /tmp/popnx-skill-d0n9x1n-hexo-blog-encrypt-1e1ae52 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-d0n9x1n-hexo-blog-encrypt-1e1ae52/skills/hexo-encrypt-toc' ~/.claude/skills/hexo-encrypt-tocChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 hexo-encrypt-toc 文件夹放到 ~/.agents/skills/hexo-encrypt-toc
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/d0n9x1n/hexo-blog-encrypt.git /tmp/popnx-skill-d0n9x1n-hexo-blog-encrypt-1e1ae52 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-d0n9x1n-hexo-blog-encrypt-1e1ae52/skills/hexo-encrypt-toc' ~/.agents/skills/hexo-encrypt-tocChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/d0n9x1n/hexo-blog-encrypt.git /tmp/popnx-skill-d0n9x1n-hexo-blog-encrypt-1e1ae52 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-d0n9x1n-hexo-blog-encrypt-1e1ae52/skills/hexo-encrypt-toc' ~/.agents/skills/hexo-encrypt-toc复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 hexo-encrypt-toc
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/d0n9x1n/hexo-blog-encrypt.git /tmp/popnx-skill-d0n9x1n-hexo-blog-encrypt-1e1ae52 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-d0n9x1n-hexo-blog-encrypt-1e1ae52/skills/hexo-encrypt-toc' ~/.cursor/skills/hexo-encrypt-toc适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月18日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: hexo-encrypt-toc
description: Patches any Hexo theme so its table of contents works with hexo-blog-encrypt without leaking encrypted headings. Use when a theme shows an empty, hidden, or plaintext TOC on password-protected posts, when installing hexo-blog-encrypt on a theme with a TOC, or when asked to "fix TOC for encrypted posts". Do NOT use for themes with no TOC, or for changing the encryption plugin itself.
---
# Encrypted-post TOC for any Hexo theme
hexo-blog-encrypt replaces `page.content` with ciphertext in an
`after_post_render` filter, sets `page.encrypt = true`, and keeps the plaintext
in `page.origin`. After the reader decrypts, it swaps in the post as
`#hexo-blog-encrypt.hbe-decrypted-content` and dispatches `hexo-blog-decrypt`
on `window`.
That breaks theme TOCs in one of three ways:
| Symptom | Cause | Risk |
| --- | --- | --- |
| TOC empty or missing | `toc(page.content)` sees ciphertext | Cosmetic |
| TOC visible on the locked page | `toc(page.origin)` rendered | **Plaintext headings published** |
| TOC hidden, appears after decrypt | `toc(page.origin)` with `display:none` | **Plaintext headings published** (view source) |
The goal is always the same: **no encrypted heading in the generated HTML, and
a working TOC after decryption.** This procedure works for any theme; the
per-theme notes in [Per-theme examples](#per-theme-examples) are examples, not a
whitelist. Everything the procedure needs is in this one file: the builder
script is [Appendix A](#appendix-a-hbe-tocjs) and the leak checker is
[Appendix B](#appendix-b-check-toc-leakjs).
## 1. Locate the TOC
Run from the Hexo site root. Include theme packages installed from npm.
```bash
THEME=$(sed -n 's/^theme:[[:space:]]*//p' _config.yml | tr -d "\"'")
grep -rnE "toc\(|\.origin|encrypt|tocbot|hexo-blog-decrypt|hbe|password" \
"themes/$THEME" "node_modules/hexo-theme-$THEME" 2>/dev/null \
| grep -v -E "/(node_modules|source/lib|vendor)/" | head -80
```
Also search component packages the theme depends on (for example Icarus
renders its TOC from `hexo-component-inferno`).
Classify every hit:
- **Server TOC**: a template calls `toc(...)` (ejs, njk, pug, jsx, swig).
- **Client TOC**: JavaScript scans headings in the DOM (tocbot, a custom
`querySelectorAll('h1,h2,…')`, or a theme `initTOC` function).
- **Theme-native encryption**: the theme has its own `password` handling or
bundles a copy of hexo-blog-encrypt. Resolve this first (see step 5).
Record the TOC container selector, the `class` passed to `toc()` (default
`toc`), and the function that starts scrollspy or highlighting.
## 2. Remove every plaintext source
In each server template:
- Delete any `toc(page.origin)`, `toc(post.origin)`, or equivalent.
- Guard the remaining call with the encrypt flag and **still output the empty
container**, because many themes drop the sidebar panel when the TOC is
empty:
```ejs
<div id="toc" class="toc-article">
<% if (!page.encrypt) { %><%- toc(page.content, {class: 'toc'}) %><% } %>
</div>
```
Nunjucks: `{% if not page.encrypt %}…{% endif %}`. Pug:
`if !page.encrypt` with the container outside the branch. JSX: pass `''`
instead of `origin`.
Also check `head` templates for `open_graph()` and meta descriptions, and
search, feed, and sitemap generator configs for fields that read `origin`,
`raw`, or `_content`.
## 3. Rebuild the TOC after decryption
Prefer the theme's own initializer. Otherwise use the generic builder.
**Client TOC (tocbot style).** Make sure the decrypted node is inside the
scanner's content selector, then refresh:
```html
<script>
window.addEventListener('hexo-blog-decrypt', function () {
var el = document.getElementById('hexo-blog-encrypt');
if (el) el.classList.add('markdown-body'); // match the theme's contentSelector
if (window.tocbot) tocbot.refresh();
});
</script>
```
**Server TOC.** Write the builder from [Appendix A](#appendix-a-hbe-tocjs) to
`themes/$THEME/source/js/hbe-toc.js` (or the theme's equivalent asset folder)
and load it on post pages after the theme's own scripts:
```html
<script>
window.HBE_TOC = {
container: '#toc', // the empty container from step 2
className: 'toc', // the class the theme passed to toc()
onRender: function () { /* call the theme's scrollspy init here */ }
};
</script>
<script src="/js/hbe-toc.js"></script>
```
The builder emits the same markup as Hexo's `toc()` helper, so theme CSS
applies. It reads heading text with `textContent` and never `innerHTML`. It
runs on the decrypt event and once on load, which covers `autoSave` pages that
decrypt from a cached key before the theme's script runs.
**Event rules for any custom handler:**
- Do not depend on `event.detail`; some forks dispatch a plain `Event`.
- Also check for `#hexo-blog-encrypt.hbe-decrypted-content` at load time.
- On PJAX themes, re-run the handler after each page swap.
## 4. Verify
```bash
hexo clean && hexo generate
# Write Appendix B to a temporary file first, e.g. /tmp/check-toc-leak.js
node /tmp/check-toc-leak.js --source source/_posts --public public
```
The checker reads every post with a front-matter `password`, extracts its
Markdown headings (code fences skipped, headings shorter than 4 characters
ignored), and searches all generated `.html`, `.xml`, `.json`, `.txt`, and
`.js` files. Pass tag-encrypted posts explicitly with `--post <file>`. Add
`--body` to also check every prose line of 40+ characters (search indexes,
feeds, metadata). Exit code 1 means a leak; fix it before deploying. A heading that also appears in
an unencrypted post is a false positive; confirm by viewing source.
Then in a browser:
1. Open an encrypted post: the TOC is empty or hidden, and view-source shows no
headings.
2. Enter the password: the TOC appears, links scroll to headings, scrollspy
highlights the current section.
3. With `autoSave: true`, reload: the TOC appears without a password.
4. Open an unencrypted post: the TOC is unchanged.
## 5. Pitfalls
- **Theme-native encryption** (for example Keep's `password` filter, or
Redefine's bundled copy of hexo-blog-encrypt): use one system. With both,
posts can be encrypted twice or the plugin's form never renders. Remove or
disable the theme's copy, or don't install the plugin.
- **Hidden is not secret.** `display:none`, `hidden`, and CSS-only tricks still
publish headings.
- **Stale hooks.** Themes written for plugin v3 may wait for elements that v4
no longer outputs (for example `hbe-prefix`). Replace them with the
`hexo-blog-decrypt` listener.
- **Theme updates** overwrite edits in `themes/<name>`. Prefer the theme's
override mechanism (`source/_data`, injectors, custom layouts) or record the
patch so it can be re-applied.
## Report back
State the theme and version, the files changed, the checker's output, and the
browser checks you ran. Say which checks you could not run.
## Per-theme examples
Examples gathered from each theme's default branch on 2026-10-12. Line
numbers drift; re-run the step 1 search before editing. Themes not listed here
use the same procedure.
| Theme | TOC source | Type | Leaks today? | Re-init after decrypt |
| --- | --- | --- | --- | --- |
| NexT | `layout/_macro/sidebar.njk` `toc(page.content, {class: 'nav'})` | Server | No (empty) | `NexT.utils.registerSidebarTOC()`, `NexT.utils.activateSidebarPanel(0)` |
| Butterfly | `layout/includes/widget/card_post_toc.pug` | Server | **Yes, hidden** `toc(page.origin)` | Build into `#card-toc .toc-content` before the theme's own `hexo-blog-decrypt` listener runs `forPostFn()` |
| AnZhiYu | `layout/includes/widget/card_post_toc.pug` | Server | **Yes, hidden** `toc(page.origin)` | Build into `#card-toc .toc-content`, then call the theme's `scrollFnToDo()` |
| Fluid | `layout/_partials/post/toc.ejs` | Client (tocbot, `.markdown-body`) | No | Add `markdown-body` to `#hexo-blog-encrypt`, then `Fluid.boot.refresh()`. The theme's `hbe-prefix` hook is from plugin v3提问、分享技巧或报告无法使用。按“有帮助”数量排序。