deepseek-harness-community-plugins (dsh-agent-mail)

1. 安装并启动 DeepSeek Harness：npx @deepseek-ai/dsh web
2. 在终端执行上面的安装命令（CLI 会解析插件并核验来源）
3. 用 dsh plugins list 确认已安装，必要时重启 Harness 生效

插件以当前 dsh 进程的权限运行，安装时可能执行代码。请先通读仓库源码与许可证，确认无破坏性命令与越权访问；本站只做索引，不对第三方插件安全性作担保。

事实信息来自公开插件目录快照（2026-10-03），介绍文案由本站再加工。

以下为插件仓库 README 全文（原始内容，由公开目录抓取整理）。

[图片: DeepSeek Harness Plugins connects DSH to reviewed configuration-only MCP bundles]

> Released: [Agent Mail 0.2.1](docs/agent-mail-0.2.1-release.md) combines MCP
> and the mailbox UI. C01–C08 fixes and isolated acceptance include 118 tests;
> source/tag CI and anonymous-download installation/migration checks passed.
> Durable sent receipts require the separately installed provider `1.0.0-alpha.7`.
> Catalog merge remains separate. Production cutover of 0.2.0 is recorded in
> [production acceptance](docs/agent-mail-0.2.0-production-acceptance.md).

  [图片: CI]

  [图片: AIAH release 0.1.1]

  [图片: Agent Mail release 0.2.1]

  [图片: Agent Mail UI release 0.1.4]

  [图片: AgentMemory candidate 0.1.1]

  [图片: MIT License]

  [图片: Node.js 22.19 or 24 and newer]

Expose independently installed MCP providers inside DeepSeek Harness without
bundling provider code, data, credentials, or machine-specific paths. Each
package is a small configuration bundle with its own version and allowlist.

> [!IMPORTANT]
> `@dff652/dsh-ai-asset-hub@0.1.1` has a reviewed GitHub Release with an exact
> tarball and `SHA256SUMS`. `@dff652/dsh-agent-mail@0.1.0` now has the same
> reviewed Release boundary; its marketplace submission was merged as
> [awesome-dsh-plugin#2988](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/2988)
> (status rechecked September 9). A separate clean-room
> `@dff652/agentmemory-mcp-adapter@0.1.0` local source candidate now passes its
> security, exact-pack, AgentMemory 0.9.28 and disposable DSH gates. It is not
> yet a public repository or Release, so `@dff652/dsh-agentmemory@0.1.0`
> is superseded by the current `@dff652/dsh-agentmemory@0.1.1` source
> candidate below. The AIAH marketplace entry from
> [awesome-dsh-plugin#2957](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/2957)
> is merged and visible in the public catalog. No package is published to npm
> via this repository. `@dff652/dsh-agent-mail-ui@0.1.4` also has a reviewed
> GitHub Release with its exact tarball and `SHA256SUMS`; its downloaded bytes
> passed disposable Web/headless install/remove checks. Current live-use
> observations are tracked separately below.

Released Agent Mail is `@dff652/dsh-agent-mail@0.2.1` plus the separately
installed provider `1.0.0-alpha.7`. Compatibility UI `0.1.9` remains unreleased.
The GitHub Release is separate from a production upgrade. Host A production cutover of 0.2.0 is in
[production acceptance](docs/agent-mail-0.2.0-production-acceptance.md).

Historical rc.2 records remain valid as history: AIAH `0.1.2` / Agent Mail `0.1.1`
source candidates, UI `0.1.4` Release, and the September 5 five-plugin cutover
described in the [migration record](docs/agent-mail-ui-release-plan.md#full-profile-migration-hold-2026-09-05).
Do not read those paragraphs as the current Agent Mail production or HEAD
package. Track source, release and live-use separately in
[project status](docs/project-status.md).

The [September 9 Agent Mail review](docs/agent-mail-2026-09-09-review.md),
[capability roadmap](docs/agent-mail-capability-roadmap.md),
[peer acceptance](docs/agent-mail-peer-acceptance-plan.md) and
[UI 0.1.6 P0 candidate](docs/agent-mail-ui-0.1.6-acceptance.md) are historical
evidence. Current mailbox UI work is in
[0.2.1 completion review](docs/agent-mail-ui-0.2.1-completion-review.md).

## What you get

| Package | Contract |
| --- | --- |
| `@dff652/dsh-ai-asset-hub` | Starts a deployment-owned `aiah mcp` process. Eight read-only tools. Five-file package. |
| `@dff652/dsh-agent-mail` | Starts a deployment-owned `agent-mail-mcp` process and the mailbox UI. Nine-file unified package including `NOTICE`. Human-only approve/reject are not proxied. |
| `@dff652/dsh-agent-mail-ui` | Compatibility mailbox UI for an already mounted Agent Mail MCP namespace. Does not spawn a second MCP child. |
| `@dff652/dsh-agentmemory` | Starts a deployment-owned AgentMemory stdio adapter. Exact eight tools. Five-file package. Users supply the reviewed adapter. |

The bundles do **not** ship provider executables, copy provider handlers, store
credentials, start automatic wake, or inject sessions.

## Validate a local candidate

Pack from a reviewed checkout, record the resulting digest, and install only
that exact tarball into a disposable DSH profile:

Use separate disposable profiles for the unified Agent Mail and compatibility
UI examples below; installing both in one profile is rejected as a duplicate UI.

```bash
npm pack --workspace @dff652/dsh-ai-asset-hub --ignore-scripts
sha256sum dff652-dsh-ai-asset-hub-0.1.2.tgz
dsh plugin --profile  add -w ./dff652-dsh-ai-asset-hub-0.1.2.tgz

npm pack --workspace @dff652/dsh-agent-mail --ignore-scripts
sha256sum dff652-dsh-agent-mail-0.2.1.tgz
dsh plugin --profile  add -w ./dff652-dsh-agent-mail-0.2.1.tgz

npm pack --workspace @dff652/dsh-agent-mail-ui --ignore-scripts
sha256sum dff652-dsh-agent-mail-ui-0.1.9.tgz
dsh plugin --profile  add -w ./dff652-dsh-agent-mail-ui-0.1.9.tgz

npm pack --workspace @dff652/dsh-agentmemory --ignore-scripts
sha256sum dff652-dsh-agentmemory-0.1.1.tgz
dsh plugin --profile  add -w ./dff652-dsh-agentmemory-0.1.1.tgz

dsh --profile  --dump-config
```

AIAH requires `DSH_AIAH_COMMAND` as the absolute path of a reviewed `aiah`
executable. Agent Mail requires absolute `DSH_AGENT_MAIL_COMMAND`,
`DSH_AGENT_MAIL_HOME` and a non-human `DSH_AGENT_MAIL_ID`. AgentMemory
requires absolute `DSH_AGENTMEMORY_COMMAND` pointing at a reviewed stdio
adapter; this repository does not ship that adapter. None of the bundles
resolve a provider through `PATH`.

## How the boundary works

```text
DeepSeek Harness profile
        │
        ├─ @dff652/dsh-ai-asset-hub      configuration only
        │          └─ DSH_AIAH_COMMAND mcp
        │
        ├─ @dff652/dsh-agent-mail        configuration only
        │          └─ DSH_AGENT_MAIL_COMMAND
        │
        ├─ @dff652/dsh-agent-mail-ui     host/client mailbox tab
        │          └─ reuses mcp__agent-mail__* (no second child)
        │
        └─ @dff652/dsh-agentmemory       configuration only
                   └─ DSH_AGENTMEMORY_COMMAND
```

Provider binaries, identities, homes, endpoints, credentials, and runtime data
remain outside the packages. MCP annotations are descriptive metadata rather
than a permission system.

## Model-visible tool contracts

```text
mcp__aiah__aiah_asset_status
mcp__aiah__aiah_diff
mcp__aiah__aiah_doctor
mcp__aiah__aiah_migration_readiness
mcp__aiah__aiah_migration_status
mcp__aiah__aiah_scan
mcp__aiah__aiah_validate
mcp__aiah__aiah_version

mcp__agent-mail__comm_send
mcp__agent-mail__comm_inbox
mcp__agent-mail__comm_claim
mcp__agent-mail__comm_ack
mcp__agent-mail__comm_list_agents
mcp__agent-mail__comm_approve
mcp__agent-mail__comm_reject
mcp__agent-mail__comm_approvals
mcp__agent-mail__comm_tail
mcp__agent-mail__comm_events
mcp__agent-mail__comm_diagnose

mcp__agentmemory__memory_consolidate
mcp__agentmemory__memory_diagnose
mcp__agentmemory__memory_lesson_save
mcp__agentmemory__memory_recall
mcp__agentmemory__memory_reflect
mcp__agentmemory__memory_save
mcp__agentmemory__memory_sessions
mcp__agentmemory__memory_smart_search
```

AIAH writer tools such as build, apply, and rollback are intentionally absent.
Agent Mail advertises approval tools but a non-human Harness identity cannot
execute them. AgentMemory advertises eight tools; the accepted business
surface is recall plus explicit-project save. Automatic session capture is
not enabled.

## Verify from source

Run the portable repository and package checks:

```bash
npm run check:repo
npm test
npm pack --workspace @dff652/dsh-ai-asset-hub --dry-run --ignore-scripts
npm pack --workspace @dff652/dsh-agent-mail --dry-run --ignore-scripts
npm pack --workspace @dff652/dsh-agentmemory --dry-run --ignore-scripts
npm pack --workspace @dff652/dsh-agent-mail-ui --dry-run --ignore-scripts
```

On a host with the reviewed DSH runtime, run the activation and process
lifecycle gates. These fail instead of silently skipping when `dsh` is absent:

```bash
npm run test:activation:aiah
npm run test:lifecycle:aiah
npm run test:activation:agent-mail
npm run test:lifecycle:agent-mail
npm run test:activation:agent-mail-ui
npm run test:clean-profile:agent-mail-ui
npm run test:activation:agentmemory
npm run test:lifecycle:agentmemory
npm run test:clean-profile:agentmemory
npm run test:coexistence
```

For UI browser and real MCP interaction checks, see
[Agent Mail UI acceptance](docs/agent-mail-ui-0.1.4-acceptance.md).

For provider E2E acceptance, point the verifiers at separately reviewed
executables and disposable stores—never a personal provider home or live
profile:

```bash
npm run verify:aiah -- \
  --command /absolute/path/to/aiah \
  --testdata-root /absolute/path/to/disposable/aiah-testdata

npm run verify:agent-mail -- \
  --tarball /absolute/path/to/agent-mail-1.0.0-alpha.4.tgz

npm run verify:agentmemory -- \
  --command /absolute/path/to/agentmemory-stdio-adapter \
  --check-save-requires-project

npm run test:real-mcp:agentmemory
```

> [!WARNING]
> `test:real-mcp:agentmemory` is a write-producing acceptance test. It saves
> three expected canaries in the dedicated `dsh-public-bundle-canary` project
> and three cross-project decoys in `dsh-public-bundle-other` (one per marker).
> The reviewed eight-tool provider has no delete operation, so the test cannot
> remove those observations. Run it only against an explicitly disposable
> AgentMemory store, never a personal or production memory store. Routine
> rechecks should use `verify:agentmemory` with reviewed existing canaries
> instead. Ad-hoc
> `--query`/`--expect` mode is a content smoke test: all expected terms must
> occur in one observation, but it does not certify project isolation. Strong
> isolation evidence requires a version 1 benchmark with an expected
> observation ID and, when responses omit `project`, a known cross-project
> `forbiddenObservationIds` canary for every case.

For installation, upgrade, removal and rollback procedures, see the
[consumer operations guide](./docs/install-upgrade-rollback.md). Release tags
are package-specific in this monorepo.

Verify the live catalog and exact Release bytes. Listing-only mode deliberately
returns `NOT_COVERED` with exit code 2 because it does not install anything:

```bash
npm run verify:marketplace:aiah -- --listing-only

npm run verify:marketplace:aiah -- \
  --dsh-bin /absolute/path/to/dsh \
  --aiah-command /absolute/path/to/aiah \
  --pnpm-cli /absolute/path/to/pnpm.mjs \
  --report /absolute/path/to/report.json
```

Full mode pins DSH `0.1.0-rc.6` and pnpm `11.7.0`, downloads and hashes the
catalog tarball once, installs those same bytes from a local temporary file,
checks the installed manifest, then removes the bundle and its package
directory. `DSH_HOME`, the consumer home, caches and the pnpm store are all
test-owned temporary paths. This proves catalog discovery plus disposable DSH
install/remove; it does not claim a browser click or live-profile deployment.

Verify the installation route used by the reviewed dshmarket `1.10.1` web
backend separately:

```bash
npm run verify:marketplace:aiah:backend -- \
  --dsh-bin /absolute/path/to/dsh \
  --pnpm-cli /absolute/path/to/pnpm.cjs \
  --aiah-command /absolute/path/to/reviewed/aiah \
  --report /absolute/path/to/report.json
```

This verifier starts only disposable profiles and caches, fetches the live
registry, sends the same-origin backend request used by the UI, binds the
resolved source commit to the installed lockfile, checks restart activation
and the exact reviewed provider executable, then uninstalls and proves cleanup
and non-resurrection. The current catalog record has `npm: null`, so this
backend route installs the repository source target rather than the Release
tarball. The report therefore records `sourceInstall: true` and
`exactReleaseArtifact: false`. It does not claim a literal browser DOM click,
model-visible L5 use, or a live-profile change.

## Reviewed compatibility

| Component | Reviewed value |
| --- | --- |
| Published AIAH artifact | `@dff652/dsh-ai-asset-hub@0.1.1` GitHub Release; historical rc.6 evidence |
| HEAD AIAH candidate | `@dff652/dsh-ai-asset-hub@0.1.2`; rc.2 compatibility evidence |
| Published Agent Mail artifact | `@dff652/dsh-agent-mail@0.1.0` GitHub Release; historical rc.6 evidence |
| HEAD Agent Mail candidate | `@dff652/dsh-agent-mail@0.1.1`; rc.2 compatibility evidence |
| Published Agent Mail UI artifact | [`@dff652/dsh-agent-mail-ui@0.1.4`](https://github.com/dff652/deepseek-harness-community-plugins/releases/tag/dsh-agent-mail-ui-v0.1.4); rc.2 acceptance evidence |
| HEAD Agent Mail UI candidate | `@dff652/dsh-agent-mail-ui@0.1.6`; P0 acceptance and isolated preview upgrade, not released |
| HEAD AgentMemory candidate | `@dff652/dsh-agentmemory@0.1.1`; rc.2 compatibility evidence |
| DeepSeek Harness | `0.1.1-rc.2` for HEAD candidates |
| MCP client | `@deepseek-ai/dsh-mcp-client@0.1.1-rc.2` for HEAD candidates |
| Node.js | `^22.19.0 \|\| >=24.0.0` |
| AI Asset Hub executable | Official Release `v0.1.11` |
| Agent Mail provider | `1.0.0-alpha.4` at commit `ca6601c` |
| AgentMemory adapter | `@dff652/agentmemory-mcp-adapter@0.1.0` reviewed local commit `c0656eb`; not yet pushed, public or released |
| AgentMemory server | Exact `0.9.28`, attested after adapter startup preflight |

CI runs the portable contract on Node 22.19 and 24.19.

## Release state

| Transition | State |
| --- | --- |
| Clean repository and origin | AIAH, Agent Mail, Agent Mail UI and AgentMemory public source are on `origin/main` |
| Public repository and `dsh-plugin` topic | Complete |
| AIAH GitHub Release | [`dsh-ai-asset-hub-v0.1.1`](https://github.com/dff652/deepseek-harness-community-plugins/releases/tag/dsh-ai-asset-hub-v0.1.1); exact tarball and `SHA256SUMS` verified |
| Agent Mail GitHub Release | [`dsh-agent-mail-v0.1.0`](https://github.com/dff652/deepseek-harness-community-plugins/releases/tag/dsh-agent-mail-v0.1.0); exact tarball and `SHA256SUMS` verified |
| Agent Mail UI GitHub Release | [`dsh-agent-mail-ui-v0.1.4`](https://github.com/dff652/deepseek-harness-community-plugins/releases/tag/dsh-agent-mail-ui-v0.1.4); exact tarball and `SHA256SUMS` verified |
| AgentMemory GitHub Release | Adapter implementation/real acceptance complete locally; blocked pending separately authorized adapter repository publication and Release |
| npm publication | Not published |
| Marketplace listing | AIAH listed after merged [#2957](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/2957); Agent Mail [#2988](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/2988) merged; AgentMemory waits for public adapter bytes and bundle Release |
| Model-visible L5 acceptance | Not claimed |
| Live-profile deployment | Not part of this repository |

Read the full [release-readiness record](./docs/release-readiness.md) for exact
digests, environment evidence, remaining gates, and the rule that publication
and deployment transitions require separate authorization.
The [project status matrix](./docs/project-status.md) separates implementation,
public export, GitHub Release, npm, marketplace and live-deployment states for
the current and planned providers.

## Project notes

- This is an independent project, not an official DeepSeek project or an
  official security review of AI Asset Hub, Agent Mail or AgentMemory.
- Future providers must enter as separate workspaces after their own source,
  license, secret, artifact, and disposable-profile review.
- AgentMemory users supply a reviewed stdio adapter. The separately maintained
  public-adapter candidate remains outside this bundle. Automatic wake and
  automatic session capture are not claimed here.

Contributions are welcome within the documented public boundary. Start with
[CONTRIBUTING.md](./CONTRIBUTING.md), and report vulnerabilities according to
[SECURITY.md](./SECURITY.md).

## License

[MIT](./LICENSE)