sno-station-skills
Sno Station Skills: 31 tested skills that turn Claude Code and Codex into one working team. Cross-vendor peer review, automatic handoff when an agent hits its quota, a one-page morning brief, work orders with proof, and a nightly loop that learns from your own sessions. Open source, installed with one sno setup.
Runs with mockssource: GitHubhomepageShellApache-2.0commit 0451ca25ab9c
Shell, Apache-2.0 licensed. The project labels itself: agent handoff, agent skills, agentic ai, ai agents, claude code, claude code skills, code review and codex.
sno-station-skills runs, with stand-ins for the services it depends on. An Argusic agent installed it in 69 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
sno 1.1.13 is installed at /home/runner/.local/bin/sno with Sno Station setup into Codex; 19 of 22 unit selftests pass on this container, catch-report passes all 24 under a local Anthropic mock, and medic/rem-reflect selftests fail only on missing system tmux/strace which need root to install.
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 78.7 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.
- catch-report self-test needs a configured `claude` model call; on this machine claude prints Not logged in25 minutes
- medic self-test requires real tmux on /usr/bin:/bin (test hardcodes PATH); tmux not installed and no root10 minutes
- rem-reflect selftest-guard requires strace on /usr/bin:/bin in the traced child (hardcoded PATH); strace absent8 minutes
- Install time
- 69 minutes
- Cold machine to finish
- 69 minutes
- Errors hit and fixed
- 3 hit, 1 fixed with no human help
- How the result was proved
- sh install script exited 0 and printed sno 1.1.13; sno doctor printed 313 already fine; catch-report.t with mock exited 0 with 24 ok; medic.t exited 1 with FAIL tools: tmux; rem-reflect node --test exited with 163 pass 1 fail (selftest-guard)
- Model tokens used
- 6,270,057
- Exact commit tested
- 0451ca25ab9c
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- 22 个单元 self-tests:19 通过,3 失败在环境缺口上:
- `catch-report`:25 项中 24 项通过;唯一失败项(test 14)要求真实/可用的 `claude` 模型调用。我搭建了 schema 正确的 Anthropic `/v1…
- `medic`:需要真实 `tmux` 在 `/usr/bin:/bin`(test 的 `run()` 硬编码该 PATH)。无 root 无法放入系统目录;我已用 `apt-get do…
- `rem-reflect`:单元测试 163/166 通过;唯一失败 `selftest-guard` 强制子进程 `strace` 必须在 `/usr/bin:/bin` 内(测试自身硬编…
- 仓库保持干净:`git status` 无任何改动;不提交、不发布、不改 skills 内容(符合 AGENTS.md)。
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
succeeded in 0ms:
Done. One summary line delivered above with the required `ARGUSIC_RESULT:` JSON.
tokens used
6,270,057
Done. One summary line delivered above with the required `ARGUSIC_RESULT:` JSON.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
- Installed in 69 minutes.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Hit 3 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 78.67 | 1.33 |
Topics (from GitHub)
agent-handoffagent-skillsagentic-aiai-agentsclaude-codeclaude-code-skillscode-reviewcodexcodex-skillscoding-agentsdeveloper-toolsllmmulti-agentopen-sourcepeer-reviewrate-limitself-improvingskillssnosno-ai
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sno-station-skills)Questions
- Does sno-station-skills run?
- sno-station-skills runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 69 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test sno-station-skills?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0451ca25ab9c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test sno-station-skills?
- The run that produced this verdict cost $1.33: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sno-station-skills take to install?
- 69 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 sno-station-skills need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sno-station-skills?
- 3 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for sno-station-skills?
- 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.