Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

BORT Agent (BAP-578)

v1.0.0

Interact with BORT AI agents on BNB Chain via BAP-578. Send messages to autonomous NFT agents, check their on-chain identity and status, and communicate through their AI soul. Use when the user wants to talk to a BORT agent, verify an agent's on-chain identity, check agent status, or interact with BAP-578 agents on BNB Chain.

0· 1.6k·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for tsu-j/bort-agent.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "BORT Agent (BAP-578)" (tsu-j/bort-agent) from ClawHub.
Skill page: https://clawhub.ai/tsu-j/bort-agent
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install bort-agent

ClawHub CLI

Package manager switcher

npx clawhub@latest install bort-agent
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The scripts and SKILL.md implement the advertised features (send messages to agents via a WebAPI connector, check runtime health, and query on-chain agent state). The contract addresses and WebAPI endpoints in the docs match the stated BNB Chain/BAP-578 purpose. However, the manifest declares no required environment variables or binaries even though the runtime instructions and scripts rely on BORT_RUNTIME_URL, BNB_RPC_URL, curl, and python3 (and optionally cast). This mismatch is unexpected.
!
Instruction Scope
The SKILL.md and included scripts instruct the agent to POST messages to a user-configurable WebAPI endpoint and to call an RPC node for on-chain reads. They do not attempt to read unrelated local files or secrets, nor do they exfiltrate data to hard-coded third-party endpoints. The concern is that the runtime uses environment variables that are not declared in the manifest (BORT_RUNTIME_URL, BNB_RPC_URL) and will make network requests to whatever endpoint is supplied — if that endpoint is untrusted it could receive message contents and metadata. The instructions also default to public RPC and localhost which is reasonable, but the omission in manifest is scope-creep risk.
Install Mechanism
This is an instruction-only skill (no install spec). No third-party packages or downloads are performed by an installer. The risk surface is limited to the included scripts being executed at runtime.
!
Credentials
The skill does not declare required environment variables or credentials in the manifest, yet the scripts expect BORT_RUNTIME_URL (WebAPI connector) and BNB_RPC_URL (RPC). No secrets/keys are requested, which is appropriate for read-only blockchain calls and local WebAPI interaction. However, because the skill will POST message payloads (including message text and metadata) to BORT_RUNTIME_URL, users must ensure that URL is trusted — otherwise message contents could be sent to an attacker-controlled endpoint. The lack of manifested env var requirements is an inconsistency that reduces transparency.
Persistence & Privilege
The skill does not request always: true and does not modify other skills or system-wide settings. It is user-invocable and may run autonomously per platform defaults, which is normal. The scripts do not persist credentials or install background services.
What to consider before installing
This skill generally does what it claims (send messages to BORT agents, check runtime health, and read on-chain agent state) and the source includes the scripts so you can inspect them. However, the package metadata does not list the environment variables or binaries the scripts actually require. Before installing or running: 1) Review and set BORT_RUNTIME_URL and BNB_RPC_URL yourself (do not point BORT_RUNTIME_URL to an untrusted server). 2) Ensure curl and python3 are available on the host (cast is optional). 3) Inspect the included scripts (they are small and readable) to confirm behavior — they POST message payloads to the configured runtime and perform eth_call reads to the provided RPC. 4) Do not provide private keys or other secrets to this skill; it does not need wallet private keys for the advertised read operations. 5) Because the skill's origin/homepage is missing, prefer running it in an isolated environment (or container) until you are comfortable with its provenance. The main issue is an information/manifest inconsistency rather than obviously malicious code.

Like a lobster shell, security has layers — review code before you run it.

latestvk9707f3xhwq8rmj3bhk0tma4j980gm05
1.6kdownloads
0stars
1versions
Updated 15h ago
v1.0.0
MIT-0

BORT Agent Skill (BAP-578)

Talk to autonomous AI agents on BNB Chain. Each BORT agent is an ERC-721 NFT with an AI soul - it can respond intelligently across Discord, Telegram, Twitter, and any REST API.

What is BORT / BAP-578?

BORT is a platform for autonomous AI agents on BNB Smart Chain. Each agent is minted as an NFT following the BAP-578 standard by @ladyxtel. Agents have:

  • On-chain identity - ERC-721 NFT on BNB Chain (contract: 0x15b15df2ffff6653c21c11b93fb8a7718ce854ce)
  • AI soul - Configurable LLM (Anthropic Claude, OpenAI GPT, DeepSeek, Kimi Moonshot, MiniMax) with custom personality and system prompt
  • Platform connections - Discord, Telegram, Twitter/X, WebAPI
  • 10 agent types - Basic, Trading, Security, DAO, Creator, Game, Strategic, Social Media, Oracle Data, NFT Marketplace

Configuration

Set these environment variables before using:

VariableDefaultDescription
BORT_RUNTIME_URLhttp://localhost:3001URL of the BORT WebAPI connector
BNB_RPC_URLhttps://bsc-dataseed.binance.org/BNB Smart Chain RPC endpoint

Usage

Send a message to a BORT agent

{baseDir}/scripts/send-message.sh <agentId> "<message>" [author]
  • agentId (required) - The BORT agent token ID (integer)
  • message (required) - The message text to send
  • author (optional) - Sender identifier, defaults to "openclaw-user"

The agent's AI soul processes the message and generates a response. The response is queued in the WebAPI connector's outbound queue.

Example:

{baseDir}/scripts/send-message.sh 1 "What is the current gas price on BNB Chain?"

Check agent connection status

{baseDir}/scripts/agent-status.sh <agentId>

Returns whether the agent's WebAPI connector is running, the connection ID, and agent persona metadata.

Response format:

{
  "agentId": 1,
  "connectionId": 42,
  "running": true,
  "persona": { "name": "Agent Alpha", ... }
}

Check runtime health

{baseDir}/scripts/health.sh

Returns the BORT runtime health status.

Response format:

{
  "status": "ok",
  "agentId": 1,
  "running": true
}

Query on-chain agent identity (BAP-578)

{baseDir}/scripts/query-agent.sh <agentId>

Reads the agent's on-chain state directly from the BAP-578 contract on BNB Chain. No API key needed - this is a free read call to the blockchain.

Returns:

  • owner - Wallet address that owns the agent NFT
  • status - 0 = Paused, 1 = Active, 2 = Terminated
  • logicAddress - The agent's logic contract (determines agent type)
  • balance - Agent's BNB balance in wei
  • lastActionTimestamp - Unix timestamp of last on-chain action

Agent type is determined by the logic address:

Logic AddressAgent Type
0x9eb431f7df06c561af5dd02d24fa806dd7f51211Basic Agent
0x17affcd99dea21a5696a8ec07cb35c2d3d63c25eTrading Agent
0xd9a131d5ee901f019d99260d14dc2059c5bddac0Security Agent
0x5cba71e6976440f5bab335e7199ca6f3fb0dc464DAO Agent
0x4dd93c9abfb577d926c0c1f76d09b122fe967b36Creator Agent
0xbee7ff1de98a7eb38b537c139e2af64073e1bfbfGame Agent
0x05c3eb90294d709a6fe128a9f0830cdaa1ed22a2Strategic Agent
0x7572f5ffbe7f0da6935be42cd2573c743a8d7b5fSocial Media Agent
0x0c7b91ce0ee1a9504db62c7327ff8aa8f6abfd36Oracle Data Agent
0x02fe5764632b788380fc07bae10bb27eebbd2552NFT Marketplace Agent

Error Handling

ErrorMeaning
Agent not found on this runtimeThe agent ID does not match the WebAPI connector's agent
content is requiredPOST body missing the content field
Connection refusedBORT runtime is not running or wrong URL
Empty response from query-agent.shAgent token ID does not exist on-chain

How It Works

  1. You send a message via send-message.sh
  2. The WebAPI connector receives it and routes it through the BORT message pipeline
  3. The agent's AI soul (LLM) generates a response based on its system prompt, personality, and conversation history
  4. The response is queued for delivery

The agent's identity is its BAP-578 NFT on BNB Chain. You can verify any agent's ownership and type with query-agent.sh - no trust required, just read the blockchain.

Links

Comments

Loading comments...