Base Trader
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: base-trader Version: 1.1.1 The OpenClaw AgentSkills skill bundle 'base-trader' is designed for autonomous crypto trading and exhibits behavior consistent with its stated purpose. All commands within SKILL.md and the provided shell scripts (`check-portfolio.sh`, `log-trade.sh`) exclusively interact with a local `bankr.sh` script (assumed to be another installed skill) or perform local file operations (e.g., writing to `data/trades.json`). There is no evidence of data exfiltration, malicious execution (like `curl|bash`), persistence mechanisms, or prompt injection attempts against the agent with a harmful objective. The extensive instructions in SKILL.md are prescriptive for trading logic, not for subverting the agent's security.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent could place or close crypto positions and lose funds if its analysis, market data, or token selection is wrong.
The skill instructs the agent to invoke Bankr for real buy and sell orders as part of an autonomous workflow. The artifacts provide risk rules, but do not show a hard technical approval gate or rollback for each trade.
Autonomous Trading Mode ... Execute trade ... `Buy $25 of TOKEN on Base` ... `Sell 25% of my TOKEN on Base`
Require explicit user confirmation before every trade or order, use hard wallet/spend limits outside the prompt, and default to read-only portfolio checks unless the user specifically approves execution.
Installing or invoking the skill may give the agent access to trade with wallet funds in a way that is under-declared by the metadata.
The skill relies on an existing Bankr wallet/config with authority to transact, but the registry metadata declares no primary credential and no required config paths.
Bankr API configured at `~/.clawdbot/skills/bankr/config.json` ... ETH in your Bankr wallet for gas and trading
Use a separate low-balance trading wallet, verify the Bankr credential scope, and ensure metadata or setup documentation clearly declares all wallet/config requirements.
If connected to a scheduler or heartbeat, trading-related actions could continue outside a single user request.
The skill explicitly contemplates scheduled autonomous operation for monitoring and trading, but the artifacts do not define how users enable, disable, audit, or revoke those ongoing actions.
When running autonomously (via cron or heartbeat): ... Morning Scan ... Midday Check ... Evening Review
Do not enable cron/heartbeat trading unless intentionally configured; review active Bankr automations regularly and keep a clear emergency stop procedure.
The safety of real trading also depends on the separate Bankr skill and its configuration.
The included script delegates important behavior to an external Bankr skill script that is not part of this artifact set. This is expected for a Bankr integration, but the actual trading implementation is outside this review.
BANKR_SCRIPT="$HOME/clawd/skills/bankr/scripts/bankr.sh" ... "$BANKR_SCRIPT" "Show my complete portfolio on Base"
Review and trust the Bankr skill separately before using this trading skill with funded wallets.
The local files can reveal trading history if shared, synced, or reused in future agent context.
The skill keeps a persistent local trade journal containing financial activity, trade reasons, prices, and transaction IDs.
TRADES_FILE="$(dirname "$0")/../data/trades.json" ... "amount_usd" ... "price" ... "reason" ... "tx"
Keep the data files private, redact them before sharing logs, and periodically review journal entries for accuracy.