DSH Plugins Marketplace

DSH Plugins

Plugins

/

dsh-os

P

dsh-os

Discovered

OS-level primitives for DeepSeek Harness: actions, grants, clipboard, workspace, environment, canary, triggers, evidence, memory, windows, approvals.

dsh-os

A family of OS-level primitives for DeepSeek Harness: 11 core modules (Act, Allow, Snip, Check, Nest, Trigger, Seek, Trace, Stage, Ring, Root), 5 optional modules (Help, Context, Cost, Backup, Notify), plus a thin contract, an optional UI shell, a catalog CLI and a dependency-only kit.

The modules stay small and independent: one Host service, ≤6 agent tools, zero runtime dependencies, independent semver, no cross-module imports. The contract (@perrylink/dsh-os-contract) and the optional shell are the only shared layers; the kit contains no business code.

Not affiliated with DeepSeek. DeepSeek and DeepSeek Harness are trademarks of their respective owners. These are independent community packages, published under MIT.

Terminal card: dsh-check prints "Check REGRESSION" and exits 1

Runnable in 10 minutes: examples/os-kit has two dependency-free demos — Allow + Act + Snip (deny → 30-minute Grant → allow → revoke → deny) and the Check regression gate. node examples/os-kit/demo.mjs needs only Node 22+; nothing is installed or published.

Docs: Quickstart · Validation plan · 0.2.0 smoke · Recipes (CI gate, agent writes, clipboard) · Troubleshooting.

Packages

ProductPackageStatusDesign
Actdsh-act0.1.1 MVPdesign
Allowdsh-allow0.1.2 MVP (security hardening)design
Snipdsh-snip0.2.0 (Win/mac/Linux capture)design
Check@perrylink/dsh-check0.2.0 (headless runner + diff)design
Nestdsh-nest0.1.0 MVPdesign
Triggerdsh-trigger0.2.0 (agent/fs/webhook sources)design
Seekdsh-seek0.2.0 (locator + memento providers)design
Trace@perrylink/dsh-trace0.2.0 (memento adapter)design
Stagedsh-stage0.2.0 (macOS/Windows adapters)design
Ringdsh-ring0.2.0 (webhook/ntfy/console)design
Root@perrylink/dsh-root0.1.2 MVPdesign
Helpdsh-help0.1.0 optionalinstall doctor / first run
Context@perrylink/dsh-context0.1.0 optionalcontext provider protocol
Cost@perrylink/dsh-cost0.1.0 optionaladapter for dsh-cost-meter
Backup@perrylink/dsh-backup0.1.0 optionalsnapshot manifest / restore plan
Notify@perrylink/dsh-notify0.1.0 optionalchannel registry / attention router
Shell@perrylink/dsh-os-shell0.2.0 optionalReact client (Act/Snip/Check tabs)
CLI@perrylink/dsh-os-cli0.1.0 tooldsh-os list/doctor/install
Contract@perrylink/dsh-os-contract0.1.0 libraryconstants, refs, manifest/tool validation
Kitdsh-os-kit0.1.0 meta bundleinstalls Act + Allow + Snip + Check

Check, Trace, Root, Context, Cost, Backup, Notify, Shell, CLI and Contract use the @perrylink/ scope where npm's name-similarity rules require it; the product names stay bare.

Install

# one-shot: the four core modules
dsh plugin --profile web add dsh-os-kit

# or individually
dsh plugin --profile web add dsh-act
dsh plugin --profile web add dsh-allow
dsh plugin --profile web add dsh-snip
dsh plugin --profile web add dsh-nest
dsh plugin --profile web add dsh-trigger
dsh plugin --profile web add dsh-seek
dsh plugin --profile web add dsh-stage
dsh plugin --profile web add dsh-ring
dsh plugin --profile web add @perrylink/dsh-check
dsh plugin --profile web add @perrylink/dsh-root
dsh plugin --profile web add @perrylink/dsh-trace

# optional small modules
dsh plugin --profile web add dsh-help
dsh plugin --profile web add @perrylink/dsh-context
dsh plugin --profile web add @perrylink/dsh-cost
dsh plugin --profile web add @perrylink/dsh-backup
dsh plugin --profile web add @perrylink/dsh-notify
dsh plugin --profile web add @perrylink/dsh-os-shell

# catalog CLI (no network, prints install plans)
npm i -g @perrylink/dsh-os-cli
dsh-os list
dsh-os doctor

Repository layout

packages/    one npm package per primitive
examples/    dependency-free runnable demos
docs/        design notes and the implementation contract
scripts/     scaffold, test and publish helpers

Status

Twenty packages ship a 0.1.x/0.2.x MVP: services, agent tools, tests and a bundle manifest (libraries/CLI where applicable). 0.2.0 adds the first real adapters: Check headless runner, Snip clipboard capture, Trigger agent/fs/webhook sources, Seek locator/memento providers, Stage macOS/Windows windows, Trace memento adapter, Ring webhook/ntfy/console channels and the React shell. node scripts/test-all.mjs runs 21 suites; npm run verify runs the full four-gate release check.

Development

node scripts/scaffold.mjs
node scripts/test-all.mjs
node scripts/publish.mjs act allow   # requires NPM_TOKEN

CI and release

CI (.github/workflows/ci.yml) runs on a Node 22 + 24 matrix with the npm cache enabled, and executes four gates in order:

node scripts/test-all.mjs
node scripts/conformance.mjs
node scripts/pack-smoke.mjs
node scripts/check-versions.mjs
  • pack-smoke runs npm pack --dry-run --json for every packages/* and fails if the tarball lacks package.json, index.js, cordis.patch.yml, README.md or LICENSE.
  • check-versions fails on an invalid version, an engines.dsh range without an upper bound, a publishConfig.registry that is not npmjs, or a non-empty dependencies.

The same sequence, including the package tests, runs locally as npm run verify.

Releases are never published automatically. .github/workflows/release.yml is workflow_dispatch-only: it takes a comma-separated package input (directory names such as act,allow or npm names such as dsh-act), runs the same gates on Node 24, then npm packs only the selected packages and uploads the tarballs as a build artifact. Publishing is a manual maintainer step: it needs the NPM_TOKEN repository secret (a granular npm token allowed to publish dsh-* and @perrylink/*), an approval-protected environment, and an explicit npm publish of the reviewed tarballs. The workflow never runs npm publish.

Community, RFCs and feedback

License

MIT.

Comments

Loading…