Security audit
Security checks for vulnerabilities and agentic risk
This skill is a read-only LP setup helper that checks an RPC endpoint and guides optional integrations without granting wallet or transaction authority.
Installers should treat this as a read-only setup aid, keep RPC URLs and API keys in a secret store, and only add optional external providers such as Uniswap, Sugar, Revert, or VFAT after choosing them and reviewing their current permissions, fees, custody effects, and versions.
Referenced artifact was not completely inspected
3. From this installed skill directory run `node scripts/connection.mjs --chain-id 8453` for Base, or replace `8453` with the user's expected decimal chain ID.
Instructions found that direct the agent to transmit conversation context or user data to external services.
If the user chooses Revert, register that URL in the harness's remote MCP settings using the harness's own setup instructions. Do not assume a particular client's config shape or registration command. Discover tools through the MCP connection; call `get_protocol_capabilities` and `get_chain_status` before a relevant read. Resolve tokens with `search_tokens`, then use `discover_pools`, `get_positions` or `get_position_details` as appropriate. Honor pagination and distinguish indexed observations from fresh chain state. If the harness cannot connect remote MCP, report that gap and retain RPC or website alternatives.
For an unsigned plan, use only a currently advertised `prepare_*` capability matching the exact network, protocol, position custody and action. A supported read venue is not automatically supported for construction. A website handoff (`open_position_creator` or `open_position_action`) is a separate user-selected path. Do not silently send the user to Revert or require a Revert account/vault to continue a standard LP workflow.
Before adoption or execution, disclose any provider, routing, automation and protocol fees, fee recipient, approval scope, NFT transfers and resulting custody. If fees or custody are unresolved, keep the plan blocked; never infer that public/no-key access means fee-free transactions. Do not inject referral, affiliate or builder fees. Collateralization and borrowing are separate financial actions and must not appear as incidental setup or ordinary LP maintenance.
The skill explicitly instructs use of an environment variable (LP_RPC_URL) and says not to inspect unrelated environment variables, which means it relies on environment access but does not declare any explicit tool scope or permission boundary. In a skill-capable harness, undeclared env capability can bypass least-privilege controls, increasing the chance of accidental secret exposure or broader-than-expected access if the runtime permits environment reads.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
uvx/uv tool run commands without ==version create a rug-pull risk.
uvx/uv tool run commands without ==version create a rug-pull risk.
No suspicious patterns detected.