Maintainer of this skill?
Automated security scan — not a certification.
by sno-ai
When Claude Code hits its usage limit, Codex picks the task up from the same memory. Sno Station puts Codex, Claude Code, Cursor, Hermes Agent and OpenClaw on one squad: they hand work to each other and review each other's code. Open source, runs on your computer.
# Add to your Claude Code skills
git clone https://github.com/sno-ai/sno-stationGuides for using ai agents skills like sno-station.
Last scanned: 9/23/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-09-23T09:07:40.870Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how sno-station compares with popular alternatives.
sno-station is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by sno-ai. When Claude Code hits its usage limit, Codex picks the task up from the same memory. Sno Station puts Codex, Claude Code, Cursor, Hermes Agent and OpenClaw on one squad: they hand work to each other and review each other's code. Open source, runs on your computer. It has 1,010 GitHub stars.
Yes. sno-station passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/sno-ai/sno-station" and add it to your Claude Code skills directory (see the Installation section above).
sno-station is primarily written in TypeScript. It is open-source under sno-ai on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh sno-station against similar tools.
No comments yet. Be the first to share your thoughts!
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
Read in other languages: English · 中文 · Deutsch · Español · Français · Русский · 한국어 · 日本語 · 繁體中文
Sno Station turns the agents you already use into a squad. Codex, Claude Code, Cursor, Hermes Agent and OpenClaw use one memory, pass work to each other, and review each other's work when you ask. Every night they dream, and wake up a little better.
It runs on your own computer. You install it once and keep working the way you do now. Find out more on our website, sno.ai.
Install with one command in any terminal:
curl -fsSL https://sno.ai/install | sh
Or tell your agent:
install sno.ai from GitHub
Then say Sno onboard in any Codex, Claude Code, Hermes, Cursor or OpenClaw conversation. More on installing.
New in 2.0: Tag Team. Your agents have each other now. One command puts two of them on a task: one builds, one challenges, and the work reaches you already argued over. See what changed.
sno reach pair "Fix the login redirect"
When one agent runs out, the next one carries on. Hit a rate limit halfway through a task and another agent picks it up from the same memory. You paste nothing.
Ask for a second look and you get one. Either agent can review the other's work. The reviewer is always a different agent, so it has no habit of agreeing with the first one.
Your agents dream. Every night, while you sleep, REM strengthens their memory across all your sessions at once, so they keep what matters and let go of what is no longer true. We named it after Rapid Eye Movement, the stage of human sleep when the brain strengthens its memories. Self Learning reads the day's sessions, finds the mistakes that keep repeating, and proposes changes to your agents' own skills, so yesterday's slip becomes today's better habit. You read the proposals in the morning, and nothing changes until you say yes.
It stays yours. Memory, messages and skills live on your computer. The memory is encrypted with a key that never leaves it. No account, no server, no daemon. The cloud side is optional, and the product is complete without it.
Last updated 2026-11-04. Your agents have each other now. You have been the one carrying work between them. That job just ended.
sno reach pair "Fix the login redirect"
One agent builds. The other challenges what it built. They settle the findings between themselves, so the work reaches you already argued over. Both run in tmux windows you can open and watch. Signed in to two vendors, you get one of each. Signed in to only one, you still get the pair, and the command tells you the review stayed with that vendor.
Stop watching terminals. When someone needs you, your Claude Code or Cursor status line says so:
❄ 2 need you · claude: approve
sno squad lays out the whole squad full screen: who needs you, who is working, what is finished. Agents started through Reach show the same thing in their tmux bar.
Sno Station · squad · 09:15 · 2 need you · 2 working · 2 finished
Needs you (2)
> claude web-app approve a permission · Fix the login redirect loop … 1m
codex api asked a question · Migrate the billing tables to th… 5m
Working (2)
claude docs-site Rewrite the quick-start page for the 2.0 install 12s
codex api Review the rate limiter change from the web-app age… 40s
Finished (2)
cursor infra finished · result unseen · Rotate the staging certi… 25m
claude web-app finished · Bump the UI kit to 4.2 2h
Work outlives the agent doing it. Quota, crash, closed window. The task continues in the same conversation when that can be restored, or in a new one built from the saved brief, and you get the truth about which: resumed, rebuilt or lost. And when an agent's context fills up and compacts, it still knows what it was doing and what already failed.
Approve a lesson, and the next reply already knows it. Not the next session. The next reply.
Messages wait their turn. The full text lands in the other agent's inbox first. If you are typing in that window, or the agent is compacting, the message waits there and your half-written draft stays as you left it.
Not yet: task carry-over and next-reply lessons run on Claude Code and Codex. The status line is Claude Code and Cursor. Hermes Agent and OpenClaw have not been through these journeys on real installs, and OpenClaw shows in sno squad with its state unknown.
Last updated 2026-10-23. Every line in the left column is a real complaint from r/ClaudeCode, r/codex or r/ClaudeAI in the week of October 20, 2026. The right column is what runs on our own machines, free and open source, to make it stop.
| What people said this week | What fixes it | Where |
|---|---|---|
| “Ran out of my 5-hour limit within 30 minutes.” | Stop sending the biggest model to do everything. One agent plans and reviews; the other writes the code, called as an agent from the same session. When one subscription runs dry, the other picks the task up from the same memory. | codex-coder, sno reach call |
| “Lost 10 hours of overnight work to ‘this model is at capacity’.” | At 2% of its quota the working agent writes a handover brief and wakes the other vendor's agent, which continues from the exact commit. You were asleep. | rotate-agent |
| “1,100 files, 30,000 lines. I don't have the token budget to review their PRs.” | Whoever pushes, reviews first: the author runs a review by the other vendor, in a fresh session that never saw the conversation, and fixes what comes back before anyone else looks. | peer-review |
| “A reviewer subagent checked every commit for two weeks. 86 runs, it stopped exactly one.” | A harness reviewing itself finds nothing real. The reviewer is always a different model in a different harness, with none of the author's chat. | peer-review |
| “Codex never finishes a review.” | Hard caps written into the skill: 3 rounds on code, 5 on a plan, 1 on tests, then it stops and waits for a person. A run that has written nothing for 15 minutes is killed as stalled. | peer-review, codex-coder, heartbeat |
| “Codex treats every byte like a criminal.” | Speculative safeguards, blockers and hashes are the first thing the review deletes. Nothing goes in without an observed failure asking for it. | less-is-more |
| “When Claude says it won't change something, is that reason stored anywhere Codex reads next time?” | Every finding is filed once, with a status only a human sets. A finding raised again updates its row instead of coming back as new, and earlier rulings are handed to the next review. | peer-review findings ledger |
| “It said done. Nothing happened.” | A task carries a written list of success checks, each answered pass or fail by a real run. An agent saying “done” counts for nothing. | pl work orders |
| “Tomorrow it makes the same mistake it made today.” | Every night a separate model reads the day's sessions, turns your corrections into one-line lessons, and you approve what stays. The bottleneck is us. | Self Learning (R skills) |
| “Half my subagents were glorified one-liners with a fresh context window.” | Procedures live in skills, not subagents. Two agents remain, for plan and execution, and for review, because those two splits are the ones that pay. | the whole set |
The habits in the right column are skills, installed into Claude Code and Codex by Sno Station and kept in sno-station-skills; the memory, the handoff and the nightly dreaming they rely on are this repository.
Open in public. This repository has been public since 2026-09-18. Everything here runs. Every block below says when it was last updated.
New in 2.0 · Install · How to use · [Cursor](#curs