Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Helps finish technical writing for briefs, user manuals, reports, and API documentation, while minimizing AIGC traces.
- Completes writing of technical documents
- Covers development briefs, manuals, reports, API docs
- Reduces AIGC traces for natural output
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
dsh plugin --profile web add github:zh851233/docs-mode#v2.0.0Install method: GitHub · sandbox install ok, web smoke failed (L5)
Verification & Compatibility
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| v2.1.1 | · | · | · | · | · |
| v2.0.0 | ✗ | ✗ | ✗ | ✗ | · |
v2.1.1github2026-10-25
https://github.com/zh851233/docs-mode
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v2.0.0github4 failed2026-10-19
https://github.com/zh851233/docs-mode
✗dsh 0.2.1-rc.2current2026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/zh851233/docs-mode#v2.0.0
ID: docs-mode@v2.0.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-alpha.42026-10-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/zh851233/docs-mode#v2.0.0
ID: docs-mode@v2.0.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-alpha.22026-10-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/zh851233/docs-mode#v2.0.0
ID: docs-mode@v2.0.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.22026-10-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/zh851233/docs-mode#v2.0.0
ID: docs-mode@v2.0.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/docs-mode/)``[](https://www.dsh.so/artifact/docs-mode/)``[](https://www.dsh.so/artifact/docs-mode/)``[](https://www.dsh.so/artifact/docs-mode/)`Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static low; dynamic low (authoritative when present) → overall low.
v2.1.1dsh manifestv2.1.1git2026-10-24v2.1.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalspawnShell · shell
preset/assets/screenshot-tools/screenshots.mjs:48serverProc = spawn(serverCmd, { shell: true, cwd: serverDir || process.cwd(), stdio: 'ignore' }); - warningmanifest-fs-unfenced · sandbox
preset/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
preset/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
preset/agent.cordis.ymlShell tool without a sandbox runner or policy in realm
show 3 audit findings
- lowScreenshot helper spawns an argv-provided command through a shell
assets/screenshot-tools/screenshots.mjs:48serverCmd comes from the --server-command CLI flag and is interpreted by a shell, so shell metacharacters in that string are executed. Reachability is limited: the flag is supplied by the operator/agent invoking the script, and the same agent already holds tool-bash/tool-pwsh, so no privilege is gained. It becomes relevant only if the command string is copied from untrusted repository text into the invocation.
- lowInstaller copies into $DSH_HOME at plugin load and is absent from the published files list
lib/index.js:34apply() performs an unconditional recursive copy into $DSH_HOME/.agent-presets/docs (overwriting when DSH_DOCS_MODE_FORCE=1) as a side effect of loading the plugin, outside the session workspace. Separately, package.json's `files` array omits "lib", so in the published tarball this entry point is likely not shipped at all — the code is a legacy path the bundle's own comment calls deprecated since dsh 0.2. No attacker-controlled path reaches it (entries come from readdirSync of the package's own preset/), so impact is a surprising home-directory write and dead code, not exploitation.
- lowBundle patch resolves package paths through a hardcoded ~/.dsh/profiles/desktop manifest
cordis.patch.yml:57This !!js expression (and the identical one under skill-filesystem's customSkillDirs) is evaluated by the config loader at mount. It is not attacker-influenced: it only resolves the plugin's own install directory. Its weakness is that it hardcodes $HOME/.dsh/profiles/desktop instead of honouring DSH_HOME, so on a non-default profile layout createRequire/resolve throws and the preset mount fails with no useful diagnostic.
Docs-writing agent preset; the flagged shell spawn and YAML !!js are operator-supplied path resolution, not attacker-controlled input, leaving only low hardening gaps.
Rule (2026-10-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to static/vet.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-10-24 · activity: Active
• Repo created: 2026-08-25
• Stars: ★ 4 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/zh851233/docs-mode
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).