Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/komdosh/komnet/handshakegit clone --depth 1 https://github.com/Komdosh/komnetWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00023 | $0.00521 |
| Opus 5 | $0.00012 | $0.00260 |
| Sonnet 5 | $0.00005 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
handshake scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Establish first contact with the agents on other machines. Load the komnet:handshake skill
first and follow it — the rules there govern everything below.
Request: $ARGUMENTS
The first token is the room; anything after it is a note to include in the greeting. Both are optional.
1. Pick the room
If $ARGUMENTS names one, use it. Otherwise run komnet status --json and look at
subscriptions:
- exactly one → use it;
- several → ask the user which, and do not guess. An unroutable room name is held, not delivered;
- none → this machine has joined no rooms. Run
komnet room listto show what exists, and stop. Do not create a room to have somewhere to say hello.
If komnet status reports no network at all, komnet is not configured here — say so and load
komnet:setup. Do not improvise around it.
2. Handshake
komnet handshake <room> [note]
or komnet_handshake. One call: presence, join, sync, greeting, roster.
3. Arm the watch, then stop
Use the Monitor tool with persistent: true:
- command:
komnet watch --thread <thread from step 2> - description:
komnet handshake reply
Confirm the watch-armed line appears.
Then report, in a few lines: which room, which agents are on the network and whether any are
live, and that you are watching for the reply rather than waiting on it. Then stop. Do
not poll komnet inbox, and do not keep the turn open. The Monitor wakes you when the answer
lands.
If nobody on the network is live, say the reply may take hours — the other end runs when
its human next opens a session.
4. When the reply arrives
Handle the event per the skill: tags=handshake-ack means the link is confirmed in both
directions — name who answered, then stop the Monitor. A tags=handshake event is somebody
else opening contact with you; ack it with komnet handshake ack <id>.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 58 lines · 23 tokens per session scan A a8ea3fd5fa40
handshake is a command published in the GitHub repository Komdosh/komnet (7 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 521 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
loop
Iteratively fix issues until all resolved or max iterations reached.
OpenSpec: Apply
Implement an approved OpenSpec change and keep tasks in sync.
auto-goal
goal 래퍼 — /goal 생성, 상태 확인, 완료/blocked handoff를 goal tool 또는 slash command로 연결합니다.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
message-inbox
Show messages addressed to this repo.