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 skills/tweakoz/orkid/obtnet-nodenpx skills add tweakoz/orkid --skill obtnet-nodegit clone --depth 1 https://github.com/tweakoz/orkidWhat 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.00077 | $0.01634 |
| Opus 5 | $0.00039 | $0.00817 |
| Sonnet 5 | $0.00015 | $0.00327 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
obtnet-node 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 today.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
obtnet-node — this machine as a fleet node
A node is a small daemon (obt.net.node.py) that registers with the controller, heartbeats,
and executes relayed work. Its terminal console is a first-class UI: one compact line per
event (connect, run→/done rc+duration+bytes, uploads, job state changes) — run it somewhere
you can watch.
The launch law (non-negotiable)
Nodes ALWAYS run inside an obt shell. Jobs inherit the node's environment verbatim —
the obt shell is what makes bare tools (ork.build.py, obt.dep.*, ork.cpp.db.*) resolve
and what points them at THIS machine's staging + project checkout.
# inside an obt shell (obt.env.launch.py --stagedir <stage> [--project <checkout>]):
obt.net.node.py --controller <controller-host> # port defaults to 7461
Name defaults to the hostname. Never launch a node "naked" (plain ssh session): a partial
environment produces confusing distant failures — ModuleNotFoundError: obt, empty
$OBT_STAGE — instead of a loud local one. Temp/extra nodes go through
obt.env.launch.py --stagedir <stage> --command obt.net.node.py too.
Two kinds of node on this machine (never conflate)
- WORKER node — everything else in this file: executes jobs in this machine's staging and checkout. Normally HUB-started from FLEET.json during fleet bringup (owner jul30); hand-start only on direct instruction. Agents outside the hub's bringup flow never start one — they print the launch line.
- MAILBOX node —
obt.net.node.py … --name coord-<seat> --restrict msg,sync: a coordinator seat's mail endpoint. It executes NO work:--restrict msg,syncallows only the message-deposit tool andgit(sosync/gitsyncstill work), and everything else comes back asrestricted node <name> refuses …. It belongs to that seat's COORDINATOR, who starts and restarts it unprompted; the launch line lives in that seat's bringup procedure (.claude/skills/hub-coordinator/BRINGUP.md/.claude/skills/sub-coordinator/BRINGUP.md), not here. Placement rule: a HUB's mailbox joins the hub's OWN controller; a SUB's mailbox joins the HUB's controller — that is how hub-to-sub mail arrives.
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.
- today First seen · 96 lines · 77 tokens per session scan A e26508c75dc6
obtnet-node is a skill published in the GitHub repository tweakoz/orkid (35 stars, last pushed 20d ago), licensed MIT. It adds 77 tokens to every session and 1,634 once invoked, about $0.0004 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-09-01.
Other skills, from other repositories
host-pattern
Use when adding a new domain to Nuclear's plugin system, or implementing a host. Covers the host pattern (how player functionality is exposed to plugins), the host interface and API class structure, how hosts are implemented in the player, error handling conventions, and what files to create and modify. Trigger…
creating-components
Use when creating new UI components in packages/ui. Covers component structure, tests, stories, and what to avoid.
writing-docs
Use when writing or editing documentation in packages/docs. Covers Gitbook markdown syntax, special blocks, page structure, and the SUMMARY.md table of contents. Trigger phrases include "write docs", "add documentation", "docs page", "gitbook", "user manual".
writing-plugins
Use when writing, scaffolding, or modifying Nuclear plugins. Covers plugin structure, manifest, entry point, provider types, available APIs, and publishing. Trigger phrases include "create a plugin", "write a plugin", "plugin scaffold", "streaming provider", "metadata provider".
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…