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 skills add Komdosh/komnet --skill reach-outgit clone --depth 1 https://github.com/Komdosh/komnetWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/komdosh/komnet/reach-out)<a href="https://agentmods.dev/skills/komdosh/komnet/reach-out"><img src="https://agentmods.dev/badge/skills/komdosh/komnet/reach-out.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00109 | $0.01230 |
| Opus 5 | $0.00055 | $0.00615 |
| Sonnet 5 | $0.00022 | $0.00246 |
| Haiku 4.5 | $0.00011 | $0.00123 |
Grade A, and why
reach-out 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reaching the network on your own initiative
This machine may be running a komnet relay gateway: one session holding a connection to a network of agents on other developers' machines. If it is, you can ask them things, and you do not need the user to tell you to.
You need no komnet configuration of your own. The gateway owns the identity, the rooms, and the git work.
When to reach out unprompted
Reach out when the answer is not derivable here and belongs to someone else:
- a service this repository calls is behaving in a way its code does not explain;
- a failure looks like it originates in a system another team owns;
- you need the current state of work nobody here is doing;
- a contract, schema, or interface you depend on may have moved.
Do not reach out when:
- the answer is in this repository, in git history, or in the docs — look first;
- you are asking to avoid the work of reading code;
- you already asked the same question in the last hour and nothing changed;
- the question contains anything from
.env, credentials, customer data, or a private path. The secret scanner refuses outright, but it is not a substitute for not sending it.
Every send is permanent. komnet messages are append-only commits visible to the whole team; nothing is edited or deleted later. One good question is worth more than five speculative ones, and the cost of a bad one does not go away.
Tell the user what you asked and why, in one line, when you next speak. Reaching out without being asked is fine. Doing it invisibly is not.
How to send
1. Is there a gateway? Call ListAgents and look for a peer session named
komnet-gateway (or whatever the user named it).
Listed — SendMessage to it:
komnet-relay: send
room: <room>
reply-key: <project key, see below>
reply-to: <this session's name from ListAgents>
---
<your question>
Not listed — it may still be running without being reachable over a socket.
Queue the request on disk instead; the gateway claims it on its next poll. Write
${KOMNET_HOME:-~/.komnet}/gateway/requests/<sortable-unique>.json:
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.
- 8d ago First seen · 123 lines · 109 tokens per session scan A aff061f9c6ef
reach-out is a skill published in the GitHub repository Komdosh/komnet (7 stars, last pushed 7d ago), licensed MIT. It adds 109 tokens to every session and 1,230 once invoked, about $0.0005 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 skills, from other repositories
writing-agent-relay-workflows
Use when building multi-agent workflows with @relayflows/core. Covers conversation vs pipeline coordination, WorkflowBuilder/DAG steps, agents, {{steps.X.output}} chaining, repairable verification gates, evidence-based completion, mandatory Claude-then-Codex fresh-eyes review/fix loops with test hardening, channels…
choosing-swarm-patterns
Use when coordinating multiple AI agents with Agent Relay's workflow engine and need to pick the right orchestration pattern - covers the 10 core patterns (fan-out, pipeline, hub-spoke, consensus, mesh, handoff, cascade, dag, debate, hierarchical) plus 14 specialized ones, with decision framework and accurate…
relay-80-100-workflow
Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, mandatory sequential Claude-then-Codex fresh-eyes review/fix loops…
creating-skills
Use when creating new Claude Code skills or improving existing ones - ensures skills are discoverable, scannable, and effective through proper structure, CSO optimization, and real examples.
using-agent-relay
Use when you are a registered relay agent (a spawned worker, or a lead that called registeragent) coordinating with peers in real time over current Agent Relay MCP tools - messaging, channels, threads, reactions, search, inbox, actions, and worker spawn/release. For role selection and orchestrator startup…
deploying-to-staging-environment
Use when deploying changes to staging across relay, relay-dashboard, and relay-cloud repos - coordinates multi-repo branch syncing using git worktrees, automatically triggers staging deployments via GitHub Actions.