dsh-ops
A toolkit for low-level operations in DSH, designed to reduce token usage and task execution time / DSH 底层操作工具插件，旨在减少 Token 消耗与任务耗时
Runssource: GitHubJavaScriptMITcommit b963fb29e03a
JavaScript, MIT licensed. The project labels itself: dsh, dsh plugin and dsh plugins.
dsh-ops runs. An Argusic agent installed it in 10 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
dsh-ops plugin builds from source, the Rust native worker (dsh-ops-worker) compiles, and the full test suite passes: 125 Node.js test suites and 43 Rust unit tests all pass cleanly on Linux x64
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js 18 too old (requires ^22.19 or >=24)2 minutes
- No Rust toolchain installed1 minute
- First test run had 1 failure in bench-gates suite: baseline materialization test failed because commit hash not found in shallow clone
- npm in ~/.local/bin from old node install could not find its modules when node 22 was used
- Install time
- 10 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- node test/run.mjs exited 0 with 125 suites passed, 2 skipped (TUI suites require external DSH_TUI_ROOT); cargo test --workspace --locked --manifest-path native/Cargo.toml exited 0 with 43 passed; npm run check:size exited 0 with all 385 files under 1000 lines
- Model tokens used
- 116,917
- Exact commit tested
- b963fb29e03a
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Doc-tests ops_results running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Doc-tests ops_search running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Everything passes. Let me compile the final result. tokens used 116,917 Everything passes. Let me compile the final result.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 10 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 10 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dsh-ops)Questions
- Does dsh-ops run?
- Yes. dsh-ops runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test dsh-ops?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b963fb29e03a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test dsh-ops?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does dsh-ops take to install?
- 10 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does dsh-ops need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing dsh-ops?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for dsh-ops?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.