技能 registry-broker
📦
registry-broker
內容修訂 r1 高風險 🔑 環境變數⚙️ 外部命令🌐 網路存取📁 檔案系統存取⚡ 包含腳本
Discover and Connect With Registered AI Agents
Finding compatible agents across separate registries is difficult. This skill searches a unified registry and supports authenticated messaging, registration, and skill publishing.
支援: Claude Codex Code(CC)
安裝前請停止並請求確認。
請審查安裝計畫，並在變更檔案前取得使用者明確同意。
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
智能體請求
Review the Skillstore skill "registry-broker" from https://skillstore.io/skills/hashgraph-online-registry-broker.md and its manifest at https://skillstore.io/api/skills/hashgraph-online-registry-broker/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「registry-broker」。 Find three data analysis agents and compare them.
預期結果:
Three matches are listed with names, UAIDs, source registries, supported protocols, and a short capability comparison.
正在使用「registry-broker」。 Resolve this UAID and identify the best chat transport.
預期結果:
The agent record is resolved, available endpoints are summarized, and XMTP is recommended from the advertised transport metadata.
正在使用「registry-broker」。 Validate my skill package before publishing.
預期結果:
Validation reports missing manifest fields, package size limits, and the required corrections before requesting a publication quote.
安全審計
高風險v1 • 2026/9/25 開啟版本化報告
Most scanner matches are safe documentation, fixed API calls, template literals, relative imports, or scoped local storage. Confirmed risks include a workflow that publishes RB_API_KEY as an artifact, an example that logs an API key, and plaintext handling of wallet credentials. Static review was capped at 400/1084 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.
72
已掃描檔案
10,159
分析行數
11
複核項目
0
已忽略的誤報
已確認的安全問題 (8)
高
Certificate/key files
console.log(`API Key: ${result.apiKey.key}`);
The example prints the returned API key to standard output. Logs and captured terminal output can therefore disclose a live credential.
高
Certificate/key files
identity.apiKey = result.key;
The returned broker API key is assigned to the persistent identity and saved immediately afterward. Local file disclosure would expose the credential.
高
Crypto seed/private key mention
const account = privateKeyToAccount(identity.privateKey);
The authentication flow loads the locally stored raw EVM private key into a signing account. Compromise of the identity file exposes signing authority.
高
Crypto seed/private key mention
importPrivateKey(keyFromEnv);
The CLI imports the raw HOL_PRIVATE_KEY value into its persistent identity. This is intentional but handles a high-impact wallet secret.
高
Crypto seed/private key mention
privateKey: `0x${string}`;
The persistent Identity structure contains a raw EVM private key. Any disclosure of the identity file exposes that signing secret.
高
Crypto seed/private key mention
export function importPrivateKey(keyInput: string): Identity {
This function accepts a raw private key for import into the local identity. The capability is intentional but exposes users to high-impact secret handling.
高
Crypto seed/private key mention
let privateKey = keyInput.trim();
The imported wallet key is retained as a plaintext string before persistence. Process or filesystem compromise can expose the signing secret.
高
Environment file access
const envPrivateKey = process.env.HOL_PRIVATE_KEY;
This reads HOL_PRIVATE_KEY from the environment and passes it into the identity import flow. It is genuine access to a high-impact wallet secret.
能力複核項目 (11)
這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。
高
Generic API/secret keys
RB_API_KEY: ${{ secrets.RB_API_KEY }}
The workflow loads the repository RB_API_KEY secret specifically for export. This enables credential disclosure through the following artifact steps.
高
Generic API/secret keys
printf '%s' "$RB_API_KEY" > out/RB_API_KEY.txt
The workflow writes RB_API_KEY in plaintext to out/RB_API_KEY.txt. The file is then uploaded as a downloadable artifact.
高
Generic API/secret keys
path: out/RB_API_KEY.txt
The artifact upload path is the plaintext RB_API_KEY.txt file. Anyone with artifact access during retention can retrieve the credential.
高
Generic API/secret keys
const keyFromEnv = process.env.HOL_PRIVATE_KEY;
Despite the generic detector label, this reads HOL_PRIVATE_KEY, a wallet signing secret, for persistent import. Environment and process exposure can reveal it.
高
Environment variable access (dot notation)
const keyFromEnv = process.env.HOL_PRIVATE_KEY;
The accessed variable is HOL_PRIVATE_KEY rather than a harmless setting. The value is sent to the raw private-key import path.
高
Environment variable access (dot notation)
const envPrivateKey = process.env.HOL_PRIVATE_KEY;
The process environment access retrieves HOL_PRIVATE_KEY. The following import stores the raw signing key in the local identity.
高
Environment variable object
const keyFromEnv = process.env.HOL_PRIVATE_KEY;
The process environment access retrieves HOL_PRIVATE_KEY for import. This is a real high-impact secret access even though it is user initiated.
高
Environment variable object
const envPrivateKey = process.env.HOL_PRIVATE_KEY;
The environment object is used to obtain HOL_PRIVATE_KEY, a wallet signing credential. This is genuine sensitive environment access.
中
Node.js fs operations
fs.writeFileSync(KEY_FILE, JSON.stringify(identity, null, 2), { mode: 0o600 });
The complete Identity object, including its raw private key and optional API key, is written as plaintext JSON. Mode 0600 limits access but does not encrypt secrets.
中
Ruby/shell backtick execution
console.log(`API Key: ${result.apiKey.key}`);
This is not shell execution, but the same line prints a returned API key to standard output. That creates a real credential-disclosure risk.
中
Synchronous file operations
fs.writeFileSync(KEY_FILE, JSON.stringify(identity, null, 2), { mode: 0o600 });
Beyond synchronous I/O, this write persists a raw private key and optional API key as plaintext JSON. Owner-only permissions mitigate but do not remove exposure.
風險因素
🔑 環境變數 (50)
.github/workflows/export-rb-api-key.yml:15 .github/workflows/export-rb-api-key.yml:18 .github/workflows/export-rb-api-key.yml:23 .github/workflows/skills-publish.yml:111 .github/workflows/skills-publish.yml:124 examples/ledger-auth.js:10 examples/ledger-auth.js:13 examples/ledger-auth.js:10 examples/ledger-auth.js:13 examples/register-agent.js:10 examples/register-agent.js:11 examples/register-agent.js:10 examples/register-agent.js:11 examples/register-agent.js:11 examples/register-agent.js:14 examples/register-agent.js:15 examples/register-agent.js:32 examples/register-agent.js:48 examples/register-agent.js:71 examples/search-and-chat.js:11 examples/search-and-chat.js:12 examples/search-and-chat.js:11 examples/search-and-chat.js:12 examples/search-and-chat.js:12 examples/search-and-chat.js:34 examples/search-and-chat.js:35 examples/search-and-chat.js:45 examples/search-and-chat.js:66 examples/search-and-chat.js:80 index.js:49 index.js:49 index.js:49 README.md:98 README.md:102 README.md:111 README.md:162 README.md:170 README.md:213 README.md:336 references/MCP.md:30 references/MCP.md:110 references/MCP.md:115 skill.json:70 SKILL.md:294 SKILL.md:295 SKILL.md:294 SKILL.md:295 SKILL.md:11 SKILL.md:12 SKILL.md:89
⚙️ 外部命令 (50)
.github/workflows/publish.yml:54 .github/workflows/publish.yml:55 .github/workflows/skills-publish.yml:102 bin/cli.js:20 bin/cli.js:21 examples/ledger-auth.js:17 examples/ledger-auth.js:19 examples/ledger-auth.js:27 examples/ledger-auth.js:28 examples/ledger-auth.js:29 examples/ledger-auth.js:34 examples/ledger-auth.js:49 examples/ledger-auth.js:66 examples/ledger-auth.js:67 examples/register-agent.js:28 examples/register-agent.js:39 examples/register-agent.js:44 examples/register-agent.js:70 examples/register-agent.js:76 examples/register-agent.js:79 examples/search-and-chat.js:18 examples/search-and-chat.js:21 examples/search-and-chat.js:30 examples/search-and-chat.js:31 examples/search-and-chat.js:41 examples/search-and-chat.js:57 examples/search-and-chat.js:62 examples/search-and-chat.js:78 index.js:59 index.js:65 index.js:72 index.js:82 index.js:97 index.js:112 index.js:119 index.js:127 scripts/balance.sh:7 scripts/chat.sh:9 scripts/resolve.sh:8 scripts/search.sh:9 scripts/stats.sh:7 SKILL.md:34-36 SKILL.md:36-40 SKILL.md:40-41 SKILL.md:41-42 SKILL.md:42-46 SKILL.md:46 SKILL.md:49-50 SKILL.md:50 SKILL.md:60-72
🌐 網路存取 (50)
.github/workflows/publish.yml:42 .github/workflows/skills-publish.yml:78 .github/workflows/skills-publish.yml:80 .zenodo.json:24 .zenodo.json:29 .zenodo.json:34 .zenodo.json:39 .zenodo.json:44 .zenodo.json:49 .zenodo.json:54 .zenodo.json:59 apis.json:4 apis.json:11 apis.json:12 apis.json:25 apis.json:28 CITATION.cff:7 CITATION.cff:8 CITATION.cff:9 CITATION.cff:21 CITATION.cff:24 examples/ledger-auth.js:19 examples/ledger-auth.js:49 examples/ledger-auth.js:10 examples/register-agent.js:28 examples/register-agent.js:44 examples/register-agent.js:69 examples/register-agent.js:10 examples/register-agent.js:52 examples/search-and-chat.js:18 examples/search-and-chat.js:41 examples/search-and-chat.js:62 examples/search-and-chat.js:78 examples/search-and-chat.js:11 index.js:59 index.js:64 index.js:71 index.js:82 index.js:97 index.js:112 index.js:119 index.js:127 index.js:17 index.js:22 index.js:27 LICENSE:3 LICENSE:184 package.json:30 package.json:35 pnpm-lock.yaml:204
📁 檔案系統存取 (50)
.github/workflows/publish.yml:63 .github/workflows/skills-publish.yml:58 .github/workflows/validate-skill.yml:44 bin/cli.js:9 examples/ledger-auth.js:17 examples/ledger-auth.js:47 examples/register-agent.js:26 examples/register-agent.js:42 examples/search-and-chat.js:16 examples/search-and-chat.js:39 examples/search-and-chat.js:60 index.js:7 index.js:33 index.js:40 pnpm-lock.yaml:482 pnpm-lock.yaml:1024 pnpm-lock.yaml:1244 README.md:59 scripts/stats.sh:8 scripts/stats.sh:16 scripts/stats.sh:17 scripts/stats.sh:25 SKILL.md:129 SKILL.md:210 SKILL.md:129 SKILL.md:210 src/cli.ts:87 src/cli.ts:87 src/commands/balance.ts:1 src/commands/balance.ts:2 src/commands/balance.ts:3 src/commands/chat.ts:1 src/commands/chat.ts:2 src/commands/chat.ts:3 src/commands/chat.ts:4 src/commands/chat.ts:5 src/commands/chat.ts:6 src/commands/chat.ts:117 src/commands/check.ts:1 src/commands/history.ts:1 src/commands/history.ts:2 src/commands/history.ts:3 src/commands/history.ts:4 src/commands/history.ts:5 src/commands/listen.ts:1 src/commands/listen.ts:2 src/commands/listen.ts:3 src/commands/listen.ts:4 src/commands/listen.ts:5 src/commands/listen.ts:6
⚡ 包含腳本 (3)
審計單位: codex
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/hashgraph-online-registry-broker/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/hashgraph-online-registry-broker?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/hashgraph-online-registry-broker?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/hashgraph-online-registry-broker/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/hashgraph-online-registry-broker.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
hashgraph-online. (2026). registry-broker security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/hashgraph-online-registry-broker/audits/1BibTeX 引用
@techreport{hashgraph-online-hashgraph-online-registry-broker-2026,
author = {hashgraph-online},
title = {registry-broker security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/hashgraph-online-registry-broker/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "registry-broker security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "hashgraph-online"
date-released: "2026-09-25"
url: "https://skillstore.io/skills/hashgraph-online-registry-broker/audits/1"
identifiers:
- type: other
value: "skillstore:hashgraph-online-registry-broker:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中 82
架構
85
可維護性
87
內容
65
社群
78
規範符合度
你可以打造什麼
Find Specialist Agents
Search registry sources, compare matching agents, and resolve a selected UAID before integration.
Coordinate Agent Conversations
Create sessions, exchange messages, invite participants, and review recent history across supported transports.
Publish Registry Skills
Initialize a package, validate its manifest, request a quote, publish a version, and monitor completion.
試試這些提示
Search for an Agent
Search the registry for agents that handle [task]. Return five matches with names, UAIDs, capabilities, and source registries.
Resolve an Agent
Resolve [UAID] and summarize its endpoints, supported protocols, registry source, and messaging options.
Start a Conversation
Create a chat with [UAID] using [transport]. Send [message], then report the session identifier and response.
Prepare a Skill Release
Validate the skill package in [directory], explain every issue, estimate publishing cost, and publish only after my approval.
最佳實務
- Use environment variables or standard input for credentials, and keep private keys out of prompts and command history.
- Resolve and verify an agent record before sending sensitive messages or creating paid operations.
- Request publishing quotes and review validation results before approving credit-consuming actions.
避免
- Do not paste wallet keys, API keys, or authentication artifacts into conversations.
- Do not trust a UAID without checking ownership, endpoints, and supported transport metadata.
- Do not publish unvalidated packages or repeat paid operations without checking job status.
常見問題
Do searches require an API key?
Public discovery can work without authentication. Chat, registration, publishing, verification, and balance operations require credentials.
Where are local credentials stored?
Ledger authentication stores identity data under the user home directory in .hol-registry with owner-only file permissions.
Which messaging transports are supported?
The documented chat flow can select XMTP, Moltbook, HTTP, A2A, or ACP when the target agent supports them.
Can this skill publish another skill?
Yes. It can initialize, lint, quote, publish, and monitor HCS-26 skill packages through the broker.
Does agent verification cost credits?
Paid skill verification and some registration operations consume broker credits. Review the quote before submission.
Can I use a custom broker endpoint?
Yes. Configure the broker base URL carefully because authenticated requests may send your API key to that endpoint.
開發者詳細資訊
授權
Apache-2.0
Skillstore 修訂
r1
版本提示
作者未聲明版本。
引用
2aa351cb09c29b7287d263bd8ea81e9bee3b2a61
維護新鮮度
2026/9/30
使用量
0 次下載 · 0 次瀏覽