Warden App
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
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.
If used carelessly, the agent could help initiate irreversible or risky crypto transactions.
The skill authorizes browser-driven actions that can move funds or create trading exposure. This is high-impact, but it is the core stated purpose and is paired with explicit confirmation requirements.
Supported action patterns: - Swap token A → token B - Deposit/withdraw to/from a protocol - Open/close perp position
Use only for trusted Warden sessions, review every transaction summary carefully, and require explicit approval before any final signing or confirmation.
The agent may see wallet balances, positions, and transaction prompts in the logged-in browser session.
The skill depends on an authenticated Warden session and wallet authority. That is expected for wallet automation, but it gives the agent access to sensitive account and transaction context.
User is logged into the Warden App... Wallet connection method is clear: - embedded Warden wallet, or - external wallet (e.g., MetaMask/Rabby/etc.).
Do not expose seed phrases or private keys, keep wallet prompts user-reviewed, and limit use to the intended Warden account and network.
Future wallet automation could rely on outdated or incorrect UI notes.
The skill stores reusable workflow notes that future agents may consult. This is purpose-aligned, but persistent notes can become stale or misleading if updated incorrectly.
Record the minimal set of repeatable workflows (URLs + UI landmarks) in `references/warden-ui-notes.md`.
Keep the reference file limited to non-sensitive UI landmarks, verify URLs and transaction details at runtime, and avoid storing account-specific private information.