sttr
cross-platform, cli app to perform various operations on string
Runssource: GitHubGoMITcommit a024bff2c27b
Go, MIT licensed. The project labels itself: cli, cli app, cli tool, cli utilities, decoding, developer tools, devutils and encoding.
sttr runs. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The sttr CLI is fully built and functional: go test ./... passes (ok, no test files in 3 packages, processors tests pass cached), the binary answers version, md5, base64, upper, sha256, and json-yaml commands with correct output, and no errors or missing dependencies remain.
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.
- Install time
- 3 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test ./... passed (ok), /tmp/sttr version returned 'dev', /tmp/sttr md5 'Hello World' returned b10a8db164e0754105b7a99be72e3fe5, /tmp/sttr upper 'hello world' returned 'HELLO WORLD', echo 'Hello World' | /tmp/sttr base64-encode returned 'SGVsbG8gV29ybGQ=', sttr sha256 returned correct hash, sttr json-yaml returned valid yaml
- Model tokens used
- 22,917
- Exact commit tested
- a024bff2c27b
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
name: test All operations verify correctly. Let me clean up the Go tarball and finalize. 2026-10-08T16:19:46.100828Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… exec /bin/sh -lc 'echo "Start: 16:16"; echo "Now: $(date +%H:%M)"' in /work/repo succeeded in 0ms: Start: 16:16 Now: 16:19 Everything works out of the box once Go is present. Let me compile the final report. tokens used 22,917 Everything works out of the box once Go is present. Let me compile the final report.
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 3 minutes, faster than the median of the 75 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- 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.
Of the 76 cli projects Argusic has installed and timed, sttr was the 28th fastest to reach a running state, and 69 of 76 reached one at all.
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 3 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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)
clicli-appcli-toolcli-utilitiesdecodingdeveloper-toolsdevutilsencodingencryptencryption-decryptiongojsonproductivitystringtermuxtermux-tooltransformtuitui-appzeropad
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sttr)Questions
- Does sttr run?
- Yes. sttr runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test sttr?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a024bff2c27b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test sttr?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sttr take to install?
- 3 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 sttr need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sttr?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does sttr compare with the alternatives?
- Of the 76 cli projects Argusic has installed and timed, sttr was the 28th fastest to reach a running state, and 69 of 76 reached one at all.
- Where is the evidence for sttr?
- 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.