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의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
제작자가 밝히지 않음 · SKILL.md 형식 Skill은 Claude Code, Codex, Cursor 같은 Agent Skills 지원 앱에서 써요
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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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-tocSkill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 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
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 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질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.