yan9651688/dsh-file-checksum ↗★ 0
dsh-file-checksum
Raw-file SHA-256 and SHA-512 verification tool for DeepSeek Harness
安装
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:yan9651688/dsh-file-checksum说明文档
阅读完整 README ↗dsh-file-checksum
A small, read-only DeepSeek Harness plugin that computes SHA-256 or SHA-512 for a file through the active Harness filesystem provider.
Unlike text-hashing tools, file_checksum reads the file's raw bytes without placing its contents in the model conversation. It works with the filesystem mounted by the current DSH profile, including compatible remote providers.
Install
Install directly from GitHub into a profile:
dsh plugin --profile web add github:yan9651688/dsh-file-checksum
For reproducible installs, pin a commit:
dsh plugin --profile web add github:yan9651688/dsh-file-checksum#
Then start that profile as usual:
dsh --profile web --dump-config
dsh --profile web
This repository ships plain ESM JavaScript, so a GitHub install does not need a prepare build or pnpm allowBuilds entry.
Tool
file_checksum accepts:
| Parameter | Required | Description |
|---|---|---|
file_path | yes | Absolute path, or a path relative to the current agent session workspace. |
algorithm | no | sha256 (default) or sha512. |
expected | no | Expected hexadecimal digest. The tool returns match or mismatch. |
Example prompt:
Use file_checksum to verify dist/app.tgz against this SHA-256:
The canonical result is structured for Native and Code Mode callers:
{
"path": "/workspace/dist/app.tgz",
"algorithm": "sha256",
"digest": "...",
"bytes": 12345,
"verification": "match"
}
A checksum mismatch is a successful tool result with verification: "mismatch"; missing, non-regular, oversized, or unreadable files are tool errors.
Configuration
The bundle defaults to a 64 MiB whole-file limit:
- insert:
- id: file-checksum
name: dsh-file-checksum
config:
maxBytes: 67108864
Override the row in a later profile patch to choose a different positive integer, up to 256 MiB. The limit exists because the current DSH raw-byte filesystem API returns a complete bounded file rather than a byte stream.