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/niracler/skill/note-to-blognpx skills add niracler/skill --skill note-to-bloggit clone --depth 1 https://github.com/niracler/skillWrote 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/niracler/skill/note-to-blog)<a href="https://agentmods.dev/skills/niracler/skill/note-to-blog"><img src="https://agentmods.dev/badge/skills/niracler/skill/note-to-blog.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.00092 | $0.02627 |
| Opus 5 | $0.00046 | $0.01314 |
| Sonnet 5 | $0.00018 | $0.00525 |
| Haiku 4.5 | $0.00009 | $0.00263 |
Grade A, and why
note-to-blog 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
笔记转博客
从 Obsidian Note 仓库中筛选适合发布的笔记，评估适配性，批量选题，双通道处理（快速转换 / 深度研究），并行 Agent 派发。
前置条件
| 工具 | 类型 | 必需 | 安装方式 |
|---|---|---|---|
| Python 3 | CLI | 是 | macOS 已预装 |
| PyYAML | CLI | 是 | pip install pyyaml |
| writing-assistant | skill | 否 | 由 personal plugin 提供 |
加载 skill 时不要主动检查这些工具。命令因缺少工具而失败时，再逐步引导完成安装和配置。
不适用情况
- 笔记库少于 5 篇时，手动选题更快
- 只想转换单篇已确定的笔记 — 直接运行
<skill-dir>/scripts/note-to-blog.py convert "<path>" - 博客草稿已存在，只需校对 — 使用
writing-assistant
脚本位置
所有确定性操作均由 Python 脚本处理：
<skill-dir>/scripts/note-to-blog.py (collect / convert / state subcommands)
路径配置位于 user-config.md。以下 Bash 示例中的
<PLACEHOLDER> 需要替换为该配置文件中的值。
工作流概览
步骤 1 步骤 2 步骤 3 步骤 4 步骤 5
收集 ──▶ 选择深度 ──▶ 按深度处理 ──▶ 执行 ──▶ 汇总
(script) (user) ├─ L1 浏览 (Agent Teams) (report)
├─ L2 推荐
└─ L3 深探
│
交互 ──▶ 分配处理通道 ──▶ 确认
步骤 1：收集候选笔记
使用 user-config.md 中的路径运行 collect：
python3 <skill-dir>/scripts/note-to-blog.py collect \
--note-repo "<NOTE_REPO>" \
--blog-content "<BLOG_CONTENT>" \
--project-paths <PROJECT_PATHS> \
--history-file "<HISTORY_FILE>"
脚本向标准输出写入一个 JSON 对象，包含：
candidates：所有符合条件的笔记，包含 title、summary、char_count 和 outgoing_linksclusters：具有 3 个以上入链的 wikilink 中心节点及相关笔记published_posts：现有博客文章的 title、tags 和 collectionsession_keywords：近期 Claude Code 会话的活动信号stats：total_scanned、filtered_out 和 candidates_count
读取 JSON 后进入步骤 2。
步骤 2：选择处理深度
展示数据规模并提供 Level 选项：
collect 完成：
候选笔记: {candidates_count} 篇 (总扫描 {total_scanned}, 过滤 {filtered_out})
主题簇: {clusters_count} 个 (3+ 引用 hub)
可选深度:
Level 1 浏览 直接展示候选列表，手动选择 0 额外 token
Level 2 推荐 LLM 评估 + 主题簇分析 ~2k token ← 推荐
Level 3 深探 Level 2 + 读取 hub 笔记全文 ~5k+ token
选择 Level (1-3)?
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 274 lines · 92 tokens per session scan A 9b091b2027d7
note-to-blog is a skill published in the GitHub repository niracler/skill (11 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 2,627 once invoked, about $0.0005 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…