Unaffiliated • MIT
Built around it, offered back
Four things a heavy user and vibecoder made while living inside Hermes Agent: the shortest path to a working install, this page, a field guide to what the models cost, and a toolkit for Markdown vaults. Not a product. Not a company. Not affiliated with Nous Research.
Start here — the next-step script
curl -fsSL https://hermes-contributions.technoir.cloud/0th -o 0th && sh
0th
0th never reimplements the installer. It shells out to the official one and
otherwise only reads the state of your machine, so it can tell you the one next thing to
do instead of handing you a checklist.
./0th next, in the Nous skin. Six
ship built into the Hermes CLI — press s to wear them here.
A user’s contribution, not a vendor’s pitch.
Nous wrote the agent, the installer and the docs. Everything here is the layer a newcomer needed on top, written by someone who needed it.
#1 — this page
It behaves like the CLI.
The idea, borrowed from Omarchy’s Etch, is that a page about a terminal tool should answer the keyboard. These are the Hermes CLI’s own commands and its own bindings, not an imitation of them.
-
/modelshow or change the current model -
/toolslist currently available tools -
/contextvisual context-usage breakdown -
/bgrun a prompt in a background session
Try it here: press / for the palette, ? for the shortcuts.
#2 — this page
And it wears the CLI’s skins.
A skin sets the semantic colours — background, ui_accent,
ui_tool, ui_ok, ui_warn,
ui_error — across the whole session. Six ship built into Hermes;
/skin shows or switches the active one. Only nous carries
Nous’ three published tokens — the other five are this page’s reading of
names the CLI ships without published palettes, and a test holds every text role in
every one of them above 4.5:1 contrast.
This page wears them too. Press s, or pick one.
The four parts.
These were four repositories, four domains and four services explaining the same thing to the same person. They are one repository now, and three of them redirect here.
-
onboarding
The shortest path to a working Hermes Agent, and
0th— a POSIX script that looks at your machine and names the one next thing to do, because a newcomer needs an instruction and not a checklist. -
field-guide
Which model to put in the main slot and which in the auxiliary slots, and what each costs today. Every price is read from the live Nous Portal catalogue and re-checked on every build.
-
pkm-toolkit
Four skills and a stdio MCP server that let Hermes work on a local Markdown vault — GTD, PARA, Johnny.Decimal. The filesystem is the database; nothing moves or deletes a note without a human saying so.
-
page
This one. / for the palette, ? for the shortcuts, s for the next skin.
Why any of this exists.
Ten years in technical support, most of them stood next to somebody holding a machine that would not do what they wanted. The gap between “the documentation is complete” and “a normal person can get this working” is not a documentation problem. It is a decision problem. The Hermes docs correctly describe twenty providers because there are twenty providers; the newcomer needs one of them named, with permission to change it later.
That is all any of this does. It is a heavy user’s attempt to give something back to a tool he uses every day, built the way he builds — quickly, in the open, and deployed. The best outcome is that Nous ships a first-run experience that makes the onboarding part pointless, and it gets deleted.
Three of these pages used to rot in silence.
One of them quoted a promotional model price. The promotion ended and five of its six numbers quietly became 80% of the real ones, for weeks, because nothing was watching. Now something is: every version number, installer command, model id, price and documentation link on this site is re-read from what Nous publishes on every build, and the build fails when any of them has moved.