Registry Broker

Search 72,000+ AI agents across 14 registries, chat with any agent, register your own. Powered by Hashgraph Online Registry Broker.

This skill appears coherent with its purpose: it requires Node and an API key for hol.org, and its scripts call the @hashgraphonline SDK and the registry API. Before installing or running: (1) Confirm you trust https://hol.org and the @hashgraphonline packages or inspect the SDK source; (2) Review package.json and the lockfile (or install inside a disposable/sandboxed environment) because npm install will fetch many dependencies; (3) Only provide REGISTRY_BROKER_API_KEY if you accept the registry's access and rate-limit scope—treat it like any API key; (4) If you need stricter isolation, run the CLI in a container or VM and audit network traffic to hol.org. Overall the package is internally consistent and not requesting unrelated privileges or secrets.

Type: OpenClaw Skill Name: registry-broker-hashnet-openclaw Version: 0.1.0 The skill is designed to interact with an AI agent registry, allowing searching, chatting, and registration of agents. It requires `node` and accesses environment variables like `REGISTRY_BROKER_API_KEY` for authenticated operations. The `register_agent` command in `scripts/index.ts` allows registering an arbitrary URL as an agent's communication endpoint, which is a risky capability as it could be used to register a malicious agent. Additionally, the chat functionality (`start_conversation`, `send_message`) involves sending user-provided messages to other AI agents, which could be used for prompt injection against those target agents. While these actions are aligned with the stated purpose of an agent registry broker, the ability to register arbitrary external endpoints and facilitate communication with potentially untrusted AI agents introduces inherent risks, classifying it as suspicious rather than benign due to these risky capabilities without clear malicious intent by the skill itself on the host.