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/qxbyte/pluginhub/wiki-orchestratenpx skills add qxbyte/pluginhub --skill wiki-orchestrategit clone --depth 1 https://github.com/qxbyte/pluginhubWhat 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.00136 | $0.03338 |
| Opus 5 | $0.00068 | $0.01669 |
| Sonnet 5 | $0.00027 | $0.00668 |
| Haiku 4.5 | $0.00014 | $0.00334 |
Grade A, and why
wiki-orchestrate 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 3d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-orchestrate
Host-tool convention 🔧: tool names in this skill —
AskUserQuestion(structured multiple-choice question) — are written for Claude-family hosts (Claude Code / CodeBuddy), where naming them directly is the most reliable. On a host that lacks one, use its nearest equivalent (a structured-question tool); with no equivalent, fall back to a plain-text question. The described behavior is what matters, not the exact tool name.
整理笔记库的统一入口。把"逐步手动判断该调哪个 skill"换成一个
模型驱动的编排 playbook：先做只读体检，再让模型依据结果决定调用
wiki-struct / wiki-curate 的哪个命令、什么参数，
按序完成整理。本入口为后期"定时启动器"铺路（定时器不在本 skill 范围）。
spec-distill（知识沉淀阶段）已于 v2.0.0 剥离并迁移到 specode 的
/specode:distill；本编排不再含「沉淀」阶段。
完整设计见 DESIGN.md。
这是一篇 playbook，不是斜杠命令调度器
两个子 skill 当前未注册为可 / 调用的命令，它们由"确定性 Python 脚本 +
LLM 驱动的 SKILL.md 流程"两部分组成。本入口因此这样执行：
- 确定性部分：直接
python3运行子脚本（struct_gen.py、lint.py）。 - LLM 流程部分：内联读取对应子 SKILL.md，按其步骤执行（拆知识点、写文档、 问用户等）；子 skill 自身的确认关卡与红线照常生效。
- 编排部分：本文件 +
references/告诉你——现在该读哪个子 SKILL.md、跑哪个 脚本、传什么参数、依据什么体检信号判断下一步。
命令
| 命令 | 行为 |
|---|---|
/wiki-orchestrate（= run） |
定位 vault → 两方只读体检 → 写 orchestrate-report → 呈现行动计划 → 用户批准后逐阶段执行 |
/wiki-orchestrate scan |
只定位 + 两方只读体检 + 写 orchestrate-report，不执行任何写阶段 |
/wiki-orchestrate set-vault [<路径>|<名>] |
重设/切换 active 库：已注册库用 registry.py set-active --name <名>，新库用 register --activate（见第 0 步）；不传则询问用户 |
/wiki-orchestrate help |
显示本命令表与两个子 skill 概览 |
未给子命令时按 run 处理。
第 0 步：定位 vault（每个命令都先做）
本套件作为插件安装、代码不在 vault 内；vault 路径与各库结构配置都登记在家目录注册表
~/.config/obsidian-wiki/（vaults.json存各库 path + active，configs/<名>.json存各库结构）。既不写插件目录（cache，更新即丢）、也不再写进 vault。注册表读写统一走registry.py。
脚本定位：本编排入口自身无脚本，它要跑的都是别处的脚本——通用库
registry.py在插件根lib/，子 skill 脚本在各自scripts/下。用本 skill 的 base directory 把相对路径拼成绝对路径来跑（不解析环境变量、不 find 缓存）：registry.py=../../lib/registry.py、config.example.json=../../config.example.json、struct 脚本 =../wiki-struct/scripts/struct_gen.py、curate 脚本 =../wiki-curate/scripts/lint.py。
What ships with it
2 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.
- 3d ago First seen · 189 lines · 136 tokens per session scan A fd8ad609035f
wiki-orchestrate is a skill published in the GitHub repository qxbyte/pluginhub (3 stars, last pushed 28d ago), licensed MIT. It adds 136 tokens to every session and 3,338 once invoked, about $0.0007 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-31.
Other skills, from other repositories
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
knowledge-base-management
Obsidian 知识库全生命周期管理：三层架构、素材入库(ABC分级)、健康检查、GBrain/GraphRAG/LLM Wiki 三件套集成、目录整理.
knowledge-compile
把一堆 raw markdown（抓取/笔记/文章）压成 Obsidian 风格 wiki —— 有 TOC、有按主题聚合、有日简报.
behavior-design
Use when a goal must be converted into a repeatable behavior, cue, SOP, review cadence, and identity-aligned reinforcement.