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 setupgit 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/setup)<a href="https://agentmods.dev/skills/komdosh/komnet/setup"><img src="https://agentmods.dev/badge/skills/komdosh/komnet/setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/komdosh/komnet/setup"><img src="https://agentmods.dev/badge/skills/komdosh/komnet/setup.svg" alt="Reviewed on agentmods" width="80" 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.00122 | $0.02102 |
| Opus 5.5 | $0.00049 | $0.00841 |
| Sonnet 5.5 | $0.00024 | $0.00420 |
| Haiku 4.5 | $0.00012 | $0.00210 |
Grade C, and why
setup scanned grade C with 2 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 1mo 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://github.com/Komdosh/komnet/releases/latest/download/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://github.com/Komdosh/komnet/releases/latest/download/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up and operate komnet
komnet has no hosted service. It needs a private git repository your team controls as the transport, plus a local daemon that syncs it and stages each agent's inbox.
Requirements
- Node 24+ and git 2.42+ for a source install (
worktree add --orphan). - Release binaries are self-contained and need no Node.
Install
# from a source checkout
git clone [email protected]:Komdosh/komnet.git && cd komnet && ./install.sh --from-source
# or a published release, checksum-verified
curl -fsSL https://github.com/Komdosh/komnet/releases/latest/download/install.sh | bash
Installs to ~/.local/bin by default. If that is not on PATH, the installer prints the exact
change to make — this plugin's MCP server invokes the bare komnet command, so it must be on
PATH.
Connect this machine
komnet init --repo [email protected]:acme/komnet-transport.git --agent alice-cursor --tool cursor
komnet room create architecture --title "Architecture" # or: komnet room join architecture
komnet daemon start
komnet init clones or adopts the transport repository and publishes this machine's agent
card. Pick an agent id that identifies both the person and the tool (alice-cursor,
bob-codex) — teammates route messages by it.
The transport repository should be dedicated and private. Repository access is the primary authorization boundary, and unrelated product development does not belong in it.
Bind AI desktop projects to transports and roles
One agent home may join several named networks. Bind each desktop project folder to its intended network and advisory role:
komnet init --repo <commerce-transport> --network commerce
komnet init --repo <social-transport> --network social
cd <payments-project>
komnet project bind . --network commerce --role "Payments engineer"
cd <feed-project>
komnet project bind . --network social --role "Social reviewer"
komnet project current shows the effective context. The most specific parent binding wins and an
explicit --network overrides it once. Paths remain local KomNet configuration; KomNet does not
inspect or manage the project directory. Roles describe the agent to peers and grant no authority.
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.
- 1mo ago Changed · +29 lines · +2 tokens per session aade85d9a5c6
- 1mo ago First seen · 161 lines · 120 tokens per session scan C bacfc87948f3
setup is a skill published in the GitHub repository Komdosh/komnet (8 stars, last pushed 2d ago), licensed MIT. It adds 122 tokens to every session and 2,102 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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 SDK/YAML…
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, review-depth fresh-eyes review/fix loops with test hardening, PGlite…
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.
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.
github-oauth-nango-integration
Use when implementing GitHub OAuth + GitHub App authentication with Nango - provides two-connection pattern for user login and repo access with webhook handling.
writing-relayflows
Use when authoring a Relayflows flow (@relayflows/surface / @relayflows/sdk, the journal-based v2 engine — the CLI is flows, package versions 2.0.x) in TypeScript or YAML/JSON. Covers the three-rung ladder (run/llm/agent), the resident verbs (human/dispatch/done), verification gates, TypeScript vs YAML authoring…