Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
Constrained subagent roster for DeepSeek Harness: one tool per role, each pinning a child system prompt, a capability allow-list, and a model tier. Bulk work vs team work by tool shape. 子代理名册:按角色约束系统提示词/能力范围/模型档位。
Installation
dsh plugin --profile web add github:121212165/dsh-plugin-subagent-roster#v0.2.2Install method: GitHub · runtime verified (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 |
|---|---|
| v0.2.2 | ✓ |
v0.2.2github✓ 1 runtime-verified2026-10-21
https://github.com/121212165/dsh-plugin-subagent-roster
✓dsh 0.2.1-rc.2current2026-10-21L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/121212165/dsh-plugin-subagent-roster#v0.2.2
ID: dsh-plugin-subagent-roster@v0.2.2@dsh0.2.1-rc.2 · profile: l3-fullscan
Issued: 2026-10-21 · expires: 2026-10-28
View checks & evidence
active in loader tree (150 entries)
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/dsh-plugin-subagent-roster/)``[](https://www.dsh.so/artifact/dsh-plugin-subagent-roster/)`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 medium — stricter wins → overall medium.
v0.2.2dsh manifestv0.2.2git2026-10-21v0.2.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (11)
- warningnetIp · network
bench/gateway.mjs:84const url = new URL(req.url, `http://127.0.0.1:${PORT}`) - warningnetIp · network
bench/gateway.mjs:277console.log(`[gateway] listening on http://127.0.0.1:${PORT} keys=${keys.length} budget=${BUDGET} upstream=${UPSTREAM}`) - warningfsWrite · files
bench/gateway.mjs:59fs.appendFileSync(LOG, JSON.stringify(entry) + '\n') - warningfsWrite · files
bench/regrade.mjs:45fs.writeFileSync(target, `${JSON.stringify(out, null, 2)}\n`) - warningchildProcess · code-exec
bench/run.mjs:121const result = spawnSync( - warningfsWrite · files
bench/run.mjs:71fs.writeFileSync(target, body) - warningfsWrite · files
bench/run.mjs:235fs.writeFileSync(outFile, JSON.stringify(summary, null, 2)) - warningchildProcess · code-exec
bin/roster-fanout.mjs:66const child = spawn(process.execPath, [DSH_BIN, '--profile', profile, '--json', taskFor({ role, item, contract, index, total: items.length } - warningfsWrite · files
bin/roster-fanout.mjs:116fs.writeFileSync(path.resolve(outFile), results.map((result) => JSON.stringify(result)).join('\n') + '\n') - warningfsWrite · files
lib/store.js:106fs.writeFileSync(file, `${JSON.stringify(ROLES, null, 2)}\n`, 'utf8') - warningfsWrite · files
lib/store.js:134fs.writeFileSync(temporary, `${JSON.stringify(document, null, 2)}\n`, 'utf8')
show 3 audit findings
- mediumUnauthenticated loopback roster-editing HTTP page runs by default and its handler (lib/page.js) is not in the audited source
lib/index.js:62The page persists an arbitrary roster. Saved role `prompt` becomes the child's persona and saved `description`/`id` are rendered into the parent's system prompt section by routingText(), so anyone who can reach 127.0.0.1:4317 (another local process, or a browser page issuing a cross-site request if page.js lacks Origin/Content-Type checks — page.js was not provided for review) can persist instructions into every subsequent agent turn and change model routes and tool filters within the CAPABILITIES allow-list.
- mediumdelegate resolves roles from the shipped ROLES map, so capability/tier changes written to roles.json are silently not enforced
lib/delegate.js:18registerDelegate builds the `role` enum from the loaded/edited roster, but execute() looks the role up in the module-level map built from the built-in ROLES and produces persona/toolFilter/agentOptions from that. An operator who removes a capability (e.g. write) from a role, or changes its tier, through the documented roster file or page gets a successful save and an unchanged child: the restriction is silently absent while the UI and routing text claim it applies. The reverse case throws 'unknown role' for newly added roles whose id is not shipped.
- lowDev bench gateway is an unauthenticated loopback proxy that spends stored upstream API keys and parses any body
bench/gateway.mjs:80The server accepts POST */chat/completions with no auth, origin, or content-type check, round-robins the OpenRouter keys read from OR_KEYS_FILE and writes one JSONL line per call (including the first 4000 chars of each system prompt) to bench/state/calls.jsonl. Any local process, or a browser page making a simple cross-site POST, can consume the account's quota and cause prompt content to be persisted to disk. Scope is limited: bench/ is excluded from the published package files and the listener is bound to 127.0.0.1.
Delegation enforces the built-in ROLES instead of the operator-edited roster, and the default loopback roster-editing HTTP page is not included in the audited source.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-18 · activity: Active
• Repo created: 2026-10-18
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
