プラグイン

Offline civil-service exam study panel integrating 15 upstream open-source question banks with SRS wrong-book, mock exams, essay grading, interactive knowledge graph and whitebox observability. The npm package ships no question-bank data: after install, the required set (~363 MB) is cloned from the question-bank manager (all 15 upstream repos are about 2.2 GB).

For the DSH Go phone app (https://go.dshtui.com): watches the quiz screen and pushes each answer as a heads-up notification, using an optional local answer bank.

Codex-inspired lifecycle command hooks for DSH, with explicit tool-input sharing, pre-tool deny policies, notifications, and local audit examples.

DeepSeek account-backed web search and page fetching for DeepSeek Harness sessions whose chat model runs through a third-party subscription or gateway (for example OpenCode Go): registers deepseek-account-search and deepseek-account-fetch providers that call the official Search and Fetch APIs with the signed-in DeepSeek account token, so the built-in web_search and web_fetch keep working without a DEEPSEEK_API_KEY.

Fills in a cheaper sibling route for subagent calls that name no provider, model or effort (for example Opus to Sonnet 5.5 at medium, Qwen max to Qwen flash); explicit choices and subagent_fork are left alone. Requires the subagent-model-selection policy to be enabled with the target route in its allowedModels - without it the plugin does nothing.

One-step local model onboarding plus a light harness for DSH. On load it probes loopback and private-network inference endpoints (llama.cpp, Ollama, vLLM, LM Studio), reads each model's context window and output budget from the backend, and registers the provider through settings, so a local model becomes selectable without hand-writing config. It then trims only that provider: masks the tool list through tools.restrict, drops named system-prompt sections and memory contexts, swaps the injected instruction block for a short one while preserving its first 80 and last 96 characters, and truncates tool-schema descriptions without touching structure or required fields. Cloud providers are returned as the same assembly object, untouched. The injected block is re-read from disk on every assembly, so editing the file takes effect on the next request with no reload. The panel in the plugin detail page is a live operations view: it shows whether the takeover is active and by which hook, how many characters the last assembly was trimmed from and to, and which providers are online (probed concurrently, with a real one-shot completion reporting latency and reply text per provider). If a local backend is not running, the panel offers a one-click launch: it probes the port first (never starting a duplicate), then starts the matching server (ollama serve, or a custom command you supply) detached and polls until the endpoint answers, clamping the wait to 3-600 seconds, reaping the child it just spawned if it never answers, and naming the paths it searched when it cannot find the binary. A stop button kills backends this plugin started (SIGTERM, then SIGKILL) and refuses to touch a server somebody else launched. When a model has just been downloaded and no backend exists yet, the panel can also scan the machine for .gguf files with hard caps (300 models, 20000 directory entries, Downloads only one level deep), start llama-server on the chosen one (skipping the .mmproj. vision projection and reusing a server that already answers), register the provider under the model id the backend reports, and run one real completion to prove it works. Before spawning anything it does a fit check that counts only the part of the file the GPU cannot hold: hostBytes = fileSize - VRAM, compared against max(total RAM - 2GB, free RAM). A file far larger than RAM is refused outright; a heavy host-side remainder is refused unless you confirm; the same remainder under mmap is only a warning, because the weights land in reclaimable page cache. A load-mode selector (auto / mmap / none / mlock / mmap+mlock) maps to llama.cpp --load-mode, and the default is whatever the engine picks. From 0.4.2 everything above is derived from the platform instead of assumed: home and data directories come from os.homedir() and the OS conventions (LOCALAPPDATA on Windows, ~/Library/Application Support on macOS, XDG_DATA_HOME elsewhere); backend binaries are looked up in the official install locations of each OS and can be pinned with OLLAMA_BIN, LLAMA_SERVER_BIN, VLLM_BIN or LMSTUDIO_BIN; model discovery walks DSH_LOCAL_MODELS_DIR, ~/models, ~/llama.cpp/models, ~/.cache/llama.cpp and the LM Studio data directory, with the WorkBuddy layout demoted to one candidate among them. VRAM is asked from nvidia-smi, then rocm-smi, then sysctl hw.memsize on Apple Silicon (flagged unified, so the same bytes are not charged twice), and any flip to a unified-memory budget is handled explicitly. Before building a command line the plugin runs llama-server --help once and keeps only the flags that build actually has, so older engines get --n-gpu-layers 99 and no KV quantization while newer ones get auto plus q8_0; anything it cannot probe is passed through rather than dropped. LM Studio is started with lms server start --port N rather than being lumped in with the engines that need a model argument, and vLLM gets its own --model example instead of llama.cpp syntax. Windows, macOS and Linux are all exercised in CI, including a windows-latest and a macos-latest job, because a cross-platform claim that has only ever run on one OS is not a claim. Two of those suites exist specifically to catch this machine's blind spots: one replays the whole suite with process.platform rewritten to each OS, and one deletes every advantage this development box has — no nvidia-smi, no rocm-smi, no sysctl, an empty PATH, a home directory with no models — and requires graceful degradation rather than a crash. That last one caught a real class of bug: several assertions hardcoded 'lms.exe', which cannot pass where the executable has no suffix. Measured on the reference machine: a 16.9GB 27.2B MoE with 14.5GB of VRAM holds a 285-691MB working set and sustains 76 tok/s after a 1000-2000 token warm-up, so file size alone is not a fit signal. From 0.4.3 the scanned models are shown as a table rather than a dropdown (one row per gguf, with its size and any fit warning), so you can see what is on disk before choosing. From 0.4.4 the delete button on the provider table removes the provider entry, not the weights file on disk. That distinction matters: what people actually want to clear out is the dead entry - one pointing at a port that never answered, one registered twice for the same port, one whose model file was deleted long ago - not a 15.8GB gguf. Deleting a config is undone by importing again; deleting a gguf is not. The removal goes through settings.mutate with an unset op on \['providers', id], because update merges layers: writing null there leaves a null provider key that the loader reads as a broken config rather than an absent entry, and only mutate/unset is implemented as Reflect.deleteProperty. The result is read back afterwards, because unset on a key that comes from a lower layer (the profile cordis.patch.yml or a home patch) does not delete it - it restores the inherited value, so the call succeeds while the entry stays. When the entry is still there the panel says so and points at the file to edit instead of reporting success, and a DSH whose settings service predates mutate() is told plainly rather than silently ignored. Deleting takes two clicks and clearing the confirmation is as easy as clicking another row; on success the online and baseURL caches are cleared and the tool surface is recomputed, since the provider list changed. The gguf itself is never touched by this plugin - the scanned-model table is display and selection only.VRAM reporting is driver-dependent. From 0.4.5 model discovery also reads Ollama's own storage: its blobs are named sha256-… with no extension, so extension matching could never list them. Weights are now accepted by extension OR by GGUF magic header (only dot-free files of at least 8MB, capped at 600 header reads per scan; obviously-not-weights extensions like .json/.md/.safetensors/.part are never opened). Ollama models are resolved from their manifests: the model layer is picked by mediaType application/vnd.ollama.image.model (never adapter/mmproj layers), the human-readable name is restored from the manifest path (…/qwen3/8b becomes qwen3:8b, …/latest stays bare), tags sharing one blob merge into a single row, and the metadata kv supplies name, quantization and context length. Adopting an Ollama model does not start a duplicate llama-server over the same weights: it confirms ollama serve answers on 11434 (launching it if not) and registers the provider under the tag the endpoint itself reports — the blob's sha256 name would never match anything, since 11434 lists qwen3:14b, not sha256-a8cc…. Two real-machine-only traps fixed on the way: existsSync('<file>/') returns true on Windows, so manifest-vs-directory branching now goes by parseable content instead of trailing-slash semantics; and the quantization label table had been copied from a stale ggml enum generation, labelling ggml_type 15 as Q5_K_S while ollama show reports Q4_K_M. Same-blob dedup is by (dev,ino), keeping whichever entry has a name. Verified on the reference machine: the scan goes from 1 row to 4 — qwen3:14b (8.64G) and qwen3:8b (4.87G) now appear with Q4_K_M badges — in 4ms; npm run verify exits 0 (launcher 57, portable 35, panel-host green including the linux/darwin simulated-platform runs); the new panel-host suite builds a real miniature Ollama store in tmpdir and points OLLAMA_MODELS at it, so results no longer depend on whether the test machine happens to have Ollama installed. From 0.4.6 the panel shows each model its real name instead of its file name, because some download tooling stores every weight under one generic file name, leaving the real name only inside the GGUF header. The scan now reads each file GGUF KV section - not a fixed-size head buffer, because tokenizer.ggml.tokens (hundreds of thousands of strings on a large MoE model) and the chat template push general.file_type past any window; and GGUF string arrays are interleaved (u64 length plus payload per element), so treating them as a length table walks the cursor off the rails and produces astronomically large reads. Reading and skipping are accounted separately: key names and types are always read, string values over 256KB and string arrays are only walked past without copying, non-string arrays over 64 elements are skipped outright, and a cursor past the file size stops the read, because an out-of-range position means the cursor is wrong rather than that a limit should be raised. The displayed name goes Ollama tag, then general.basename plus size_label, then general.name, then the file name, with the full string kept for the hover text since it usually carries internal build numbers; mmproj files are now identified by general.type as well as by name. A short read (truncated file) no longer feeds half a value into the parser. On the reference machine, reading one file header parses 44 keys in about 16ms, and a whole scan takes about 31ms. From 0.4.7 the smoke test no longer fails the first time and passes the second. The old code gave both request attempts one shared AbortController and one shared 30-second timer, so the total budget covered both rounds: a cold load of a large model burned it in round one, the abort left the signal permanently aborted, and the second round (the Ollama-style reasoning_effort: none retry) could not even be sent - which is exactly why the first click returned This operation was aborted and the second succeeded. Now each attempt gets its own controller and timer, a timeout retries once automatically (retryOnTimeout, on by default) because a first-request timeout almost always means the weights are still being read from disk, and non-timeout errors (refused connection, HTTP error) are not retried at all. Timeouts report themselves: the message says the wait exceeded smokeTimeout, whether a retry already happened, and points at the new smokeTimeout setting (seconds, default 60, clamped to 5-600) - port responding is not the same as tokens coming out, so it is a separate knob from launchTimeout. Unrelated: an example naming one specific model was dropped from the panel copy, since not every machine has that model downloaded, and the explanation now describes the mechanism instead. From 0.4.8 adopting a plain .gguf no longer registers an unrelated Ollama model. The port field used to follow the last click rather than the file: selecting an Ollama entry moved it to 11434, selecting a plain .gguf did not move it back, so a 11434 left over from an earlier click stayed. The server accepted it as given, probed the port, found Ollama answering and borrowed it (the skipped-launch log line about the port already answering is this path), and then the model id - derived from the file name - could not be matched against Ollama's /v1/models, where the fallback was to grab the first entry in the list. Embedding models tend to sort first, so the adopt registered a model the user never selected. Now the port follows the file: a plain .gguf landing on another engine's port (ollama 11434, vLLM 8000, LM Studio 1234) is moved to 8090 and the panel says so. Only ports belonging to a known engine are overridden - a hand-typed 9999 aimed at your own llama-server is left alone. The model-id fallback no longer guesses either: it takes the only entry when there is exactly one (a single-model backend may legitimately report a different id than the file name) and otherwise reports an error listing the ids it did see, rather than registering a wrong provider.

Looks up English words in chat replies by click or selection, showing part of speech, Chinese meaning and exam tags; selecting a pure-English sentence translates it. Ships an offline dictionary: 20,499 entries, 8,960 with bilingual examples, 6,374 with root analysis.

ひな型としてコピーできるスタータープラグインです。右サイドバーのタブ1つ、2言語、実際のbundleをマウントする動作テスト、manifest preflightを実行するCIを備えます。

DSHの会話内にあるObsidian vaultファイルを通常クリックすると、ノートはObsidianアプリで、.texなど設定済みの種類はプロジェクトフォルダーをworkspaceとしてVS Codeで開きます。Cmd/Ctrlクリックではアプリ内プレビューを維持します。open_vault_fileツールも同じ振り分けを行い、すべてのオープン操作は設定済みのvaultRoot内に限定されます。

INDEXの絶対パスとversionを含む短い規約リマインダーを、session/版ごとに1回注入します。規約versionが変わると次のturn（chat turnを含む）で再注入します。任意のhard guardではoperation相当turn中、sessionがindexを読むまでwrite/edit toolを拒否します（既定ではchat turnとshellはブロックしません）。例のchecklistか指定ディレクトリを使い、依存なし、path設定可能。作業開始時に規約が参照されない問題に対処します。

投資リサーチbundleです。検索、ページ取得、source監査、主張検証、数値厳密性、channel健全性、workflow loader、chart engine、PDF renderer、PDF gateの10 toolsとai-berkshire由来の23 skillsを収録。6段階workflowで4つの並列agent（段永平、バフェット、マンガー、李録）が企業を調査・相互検証し、表紙、表、キャプション、ページ番号付きの図表豊富なPDFを作成します。Python 3.10+が必要。chart/PDF toolにはpython-docxとmatplotlibも必要です。

skillにtagを付けて絞り込む仕組みです。boolean tag expressionが選んだ部分集合だけを各workspace/sessionへ渡します（例: `pdf + docx`、`aegis * plugin`）。除外skillは設定画面で隠すだけでなく、model catalogからdeny-shadowされます。expression外のskillは手動追加または強制無効化が可能です。同梱の`tagging-skills`は実行マシンに基づくtag集合をagentが導く方法を教えます。

DeepSeek Harnessに`principles_audit` toolを登録し、原則ライブラリのprinciple_id衝突/旧ID、因果記述・境界・反例・根拠の欠落、重複/類似原則、statusとconfidenceの不整合、長期未更新項目、観点カバー漏れを検査します。指摘を重大度順にし、hard gateでpass/warn/failを判定します。critical指摘は有効期限内の有効な例外ですべてカバーする必要があります。ライブラリは読み取り専用です。

中国の大学院入学試験「数学一」向けのSymPy厳密計算と独立検証。14ツールで214演算子を扱い、既定で厳密な記号結果を出し、各結果を別の仕組みで再検証する。Python 3.10+、sympy、mpmathが必要。

ノードベースのGLSLワークベンチ。キャンバス上でシェーダーグラフを接続してライブプレビューし、マルチパスバッファ（BufferA–D）を備えたShadertoy互換GLSLにコンパイル、編集時にホットリロードできます。HLSL / MSL / SPIR-Vにも相互コンパイルし、プロジェクト、マテリアル、スナップショット、画像・音声・歌詞などのリソースをローカルワークスペースで管理します。組み込みノード57個、同梱例8個、エージェントツール11個。ランタイム依存関係はありません。

DSH Agentの実行中にキューへ入れたユーザーメッセージを、公式キュードック内で並べ替えます。ドラッグハンドルと各行の↑／↓ボタンを使い、ホスト側で同時実行チェック付きのinbox spliceとして適用します。ドックは置換せず装飾するため、プレビュー、インライン編集、steering、削除、添付は元のまま。最後に見た後でキューが変化した場合、行がユーザープロンプトでない場合（Goalラウンド等）、またはsubagentのキューなら移動を拒否します。

DeepSeek Harness 用の独立型マルチエージェント討論。異なる気質の討論者が同調せず個別に調査し、相互反対尋問の後、審査役が結論に集約します。バックグラウンドジョブとして実行し、エージェントごとの進捗・トークン集計、wave 並列実行、セッション参照による再開に対応します。

composerボタンから、現在のセッションで利用可能な全スキルを中国語タイトル、用途、使用例とともに一覧表示します。新しくインストールしたスキルもワンクリックでカタログに追加し、ローカルに保存します。