All 96 static matches are false positives because they identify documentation links, API reference tables, environment-variable configuration, or literal CLI examples. The skill does describe an optional x402 private-key payment flow, which is a medium-risk financial side effect that requires explicit user approval and controlled credentials.
SKILL.md documents the --x402 option and asks the user to configure a private key for pay-per-call micropayments. This creates a financial side effect that should require explicit approval.
The cited line explicitly describes x402 micropayments and private-key setup. The documentation does not show unauthorized payment behavior, so the finding is limited to confirmation and fund-management risk.
Most static alerts are false positives from Markdown links, API reference tables, and documented CLI examples rather than executable skill code. Two documented actions remain material risks: global installation of a third-party npm CLI and configuration of a private key for x402 payments. No prompt-injection text or data-exfiltration intent was found.
The x402 setup asks users to configure a private key in the Chainbase CLI. This can expose a wallet credential or authorize paid requests if the CLI, its storage, or the endpoint is compromised.
The documented command explicitly configures a private key for micropayments. The resulting credential and financial authorization create a material risk beyond ordinary public-data queries.
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
**Install**: `npm install -g chainbase-cli` (or use `npx chainbase-cli`)
The skill instructs users to install a globally scoped third-party npm package. This expands the trusted supply chain and can execute package installation scripts.
**x402 Payment**: Supports pay-per-call micropayments via `--x402` flag. Setup: `chainbase config se
The skill instructs users to configure a private key for x402 payments. A private key can authorize financial transactions if entered into an untrusted or compromised CLI.
Most static URL, environment, and chain_id alerts are documentation false positives. The skill intentionally instructs agents to install and run Chainbase CLI, including remote queries, SQL, credentials, and optional x402 payment setup. No prompt injection or credential exfiltration text was found in the reviewed files.
SKILL.md documents x402 micropayments and the command chainbase config set private-key 0x.... This can lead agents or users to handle wallet private keys and paid calls during data access.
The private-key and x402 instructions are explicit in SKILL.md. The risk is contextual because the key is a placeholder and the payment mode is optional.
Capability review items (41)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
**x402 Payment**: Supports pay-per-call micropayments via `--x402` flag. Setup: `chainbase config se
The skill instructs configuring a private key for x402 micropayments. Handling a signing key in CLI configuration creates financial and credential exposure risk.
The --x402 option enables paid micropayment mode for external calls. Payment-capable command execution needs explicit user control and spending boundaries.
**Install**: `npm install -g chainbase-cli` (or use `npx chainbase-cli`)
The skill instructs users or agents to install or run a third-party npm CLI. Global npm installation and npx execution carry supply-chain and local command execution risk.
**Auth**: Set API key via `chainbase config set api-key YOUR_KEY`, or env `CHAINBASE_API_KEY`. Falls
The skill instructs configuring an API key through the CLI or environment variable. This is expected authentication, but it handles sensitive credentials through external tooling.
The code block contains chainbase CLI commands for token, ENS, and SQL queries. These commands trigger local process execution and remote Chainbase requests.
| Latest block number | `chainbase block latest` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| Wallet transaction history | `chainbase tx list <address>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| List of holder addresses | `chainbase token holders <contract>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| Top token holders / who holds a token | `chainbase token top-holders <contract>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| Token transfer history | `chainbase token transfers --contract <addr>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| ENS domains held by address | `chainbase domain ens <address>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| Space ID resolve (BSC) | `chainbase domain spaceid-resolve <domain>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| Space ID reverse (BSC) | `chainbase domain spaceid-reverse <address>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
- If unknown, use `chainbase token metadata <contract>` or ask the user for the contract address
The line tells the agent to run a chainbase token metadata command when a contract is unknown. This is legitimate but still an external command based on task context.
Query crypto social signals via `chainbase tops`. No API key required — free to use.
The line directs use of the chainbase tops command family to query social signals. This is disclosed, but it is external command and remote network activity.
| What's trending in crypto right now | `chainbase tops trending [--language <lang>]` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| Details / summary of a specific topic | `chainbase tops topic <topic_id>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| Raw tweets / posts under a topic | `chainbase tops posts <topic_id>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| Find topics related to a narrative keyword | `chainbase tops search <keyword>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
| Recent Twitter/X mentions of a project or keyword | `chainbase tops mentions <keyword>` |
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
1. `chainbase tops trending` → get current top topics (note `id` fields)
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
3. `chainbase tops posts <id>` → retrieve raw tweets for sentiment analysis
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
1. `chainbase tops search <keyword>` → find candidate topics from a vague term
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.
1. `chainbase tops mentions <keyword>` → monitor social mentions of a project/token
The line directs use of chainbase CLI with user-provided values or remote service calls. This is legitimate for the skill, but it is real external command and network execution risk.