← Back to Skills Marketplace
1566
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install bort-agent
Description
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.
README (SKILL.md)
\r \r
BORT Agent Skill (BAP-578)\r
\r 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.\r \r
What is BORT / BAP-578?\r
\r 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:\r \r
- On-chain identity - ERC-721 NFT on BNB Chain (contract:
0x15b15df2ffff6653c21c11b93fb8a7718ce854ce)\r - AI soul - Configurable LLM (Anthropic Claude, OpenAI GPT, DeepSeek, Kimi Moonshot, MiniMax) with custom personality and system prompt\r
- Platform connections - Discord, Telegram, Twitter/X, WebAPI\r
- 10 agent types - Basic, Trading, Security, DAO, Creator, Game, Strategic, Social Media, Oracle Data, NFT Marketplace\r \r
Configuration\r
\r
Set these environment variables before using:\r
\r
| Variable | Default | Description |\r
|----------|---------|-------------|\r
| BORT_RUNTIME_URL | http://localhost:3001 | URL of the BORT WebAPI connector |\r
| BNB_RPC_URL | https://bsc-dataseed.binance.org/ | BNB Smart Chain RPC endpoint |\r
\r
Usage\r
\r
Send a message to a BORT agent\r
\r
{baseDir}/scripts/send-message.sh \x3CagentId> "\x3Cmessage>" [author]\r
```\r
\r
- `agentId` (required) - The BORT agent token ID (integer)\r
- `message` (required) - The message text to send\r
- `author` (optional) - Sender identifier, defaults to "openclaw-user"\r
\r
The agent's AI soul processes the message and generates a response. The response is queued in the WebAPI connector's outbound queue.\r
\r
**Example:**\r
```bash\r
{baseDir}/scripts/send-message.sh 1 "What is the current gas price on BNB Chain?"\r
```\r
\r
### Check agent connection status\r
\r
```bash\r
{baseDir}/scripts/agent-status.sh \x3CagentId>\r
```\r
\r
Returns whether the agent's WebAPI connector is running, the connection ID, and agent persona metadata.\r
\r
**Response format:**\r
```json\r
{\r
"agentId": 1,\r
"connectionId": 42,\r
"running": true,\r
"persona": { "name": "Agent Alpha", ... }\r
}\r
```\r
\r
### Check runtime health\r
\r
```bash\r
{baseDir}/scripts/health.sh\r
```\r
\r
Returns the BORT runtime health status.\r
\r
**Response format:**\r
```json\r
{\r
"status": "ok",\r
"agentId": 1,\r
"running": true\r
}\r
```\r
\r
### Query on-chain agent identity (BAP-578)\r
\r
```bash\r
{baseDir}/scripts/query-agent.sh \x3CagentId>\r
```\r
\r
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.\r
\r
**Returns:**\r
- `owner` - Wallet address that owns the agent NFT\r
- `status` - 0 = Paused, 1 = Active, 2 = Terminated\r
- `logicAddress` - The agent's logic contract (determines agent type)\r
- `balance` - Agent's BNB balance in wei\r
- `lastActionTimestamp` - Unix timestamp of last on-chain action\r
\r
**Agent type is determined by the logic address:**\r
\r
| Logic Address | Agent Type |\r
|---------------|------------|\r
| `0x9eb431f7df06c561af5dd02d24fa806dd7f51211` | Basic Agent |\r
| `0x17affcd99dea21a5696a8ec07cb35c2d3d63c25e` | Trading Agent |\r
| `0xd9a131d5ee901f019d99260d14dc2059c5bddac0` | Security Agent |\r
| `0x5cba71e6976440f5bab335e7199ca6f3fb0dc464` | DAO Agent |\r
| `0x4dd93c9abfb577d926c0c1f76d09b122fe967b36` | Creator Agent |\r
| `0xbee7ff1de98a7eb38b537c139e2af64073e1bfbf` | Game Agent |\r
| `0x05c3eb90294d709a6fe128a9f0830cdaa1ed22a2` | Strategic Agent |\r
| `0x7572f5ffbe7f0da6935be42cd2573c743a8d7b5f` | Social Media Agent |\r
| `0x0c7b91ce0ee1a9504db62c7327ff8aa8f6abfd36` | Oracle Data Agent |\r
| `0x02fe5764632b788380fc07bae10bb27eebbd2552` | NFT Marketplace Agent |\r
\r
## Error Handling\r
\r
| Error | Meaning |\r
|-------|---------|\r
| `Agent not found on this runtime` | The agent ID does not match the WebAPI connector's agent |\r
| `content is required` | POST body missing the `content` field |\r
| Connection refused | BORT runtime is not running or wrong URL |\r
| Empty response from `query-agent.sh` | Agent token ID does not exist on-chain |\r
\r
## How It Works\r
\r
1. You send a message via `send-message.sh`\r
2. The WebAPI connector receives it and routes it through the BORT message pipeline\r
3. The agent's AI soul (LLM) generates a response based on its system prompt, personality, and conversation history\r
4. The response is queued for delivery\r
\r
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.\r
\r
## Links\r
\r
- BAP-578 Contract (BSCScan): https://bscscan.com/address/0x15b15df2ffff6653c21c11b93fb8a7718ce854ce\r
- Platform Registry: https://bscscan.com/address/0x985eae300107a838c1aB154371188e0De5a87316\r
Usage Guidance
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.
Capability Analysis
Type: OpenClaw Skill
Name: bort-agent
Version: 1.0.0
The skill is classified as suspicious due to the `scripts/send-message.sh` script. This script sends user-provided message content to a configurable `BORT_RUNTIME_URL`. While the default URL is `http://localhost:3001`, the ability to set this environment variable to an arbitrary external endpoint means that user-provided messages, which could contain sensitive information, could be exfiltrated to an attacker-controlled server if the `BORT_RUNTIME_URL` is maliciously configured. This represents a risky capability without clear malicious intent from the skill itself, but it enables potential data exfiltration.
Capability Assessment
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.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install bort-agent - After installation, invoke the skill by name or use
/bort-agent - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
BORT Agent Skill 1.0.0 initial release:
- Enables interactions with BORT AI agents on BNB Chain using the BAP-578 NFT standard.
- Send messages to agents, check agent connection status, and verify on-chain identity and type.
- Supports 10 agent types (e.g., Trading, DAO, Oracle Data) as ERC-721 NFTs.
- Provides scripts for messaging, status checks, health checks, and on-chain queries.
- Includes error handling guidelines and clear configuration instructions.
Metadata
Frequently Asked Questions
What is BORT Agent (BAP-578)?
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. It is an AI Agent Skill for Claude Code / OpenClaw, with 1566 downloads so far.
How do I install BORT Agent (BAP-578)?
Run "/install bort-agent" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is BORT Agent (BAP-578) free?
Yes, BORT Agent (BAP-578) is completely free (open-source). You can download, install and use it at no cost.
Which platforms does BORT Agent (BAP-578) support?
BORT Agent (BAP-578) is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created BORT Agent (BAP-578)?
It is built and maintained by tsu-j (@tsu-j); the current version is v1.0.0.
More Skills