PRISM OS SDK
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill mostly looks like a financial data SDK, but supplied docs also describe agent-controlled trade execution with a wallet signer despite read-only claims.
Review this skill before installing or enabling it in an autonomous agent. It may be safe as a read-only data SDK, but only use data endpoints unless you have confirmed the execute module cannot trade; never give it wallet signer access unless you intentionally want transactions and have explicit approval controls.
Findings (3)
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.
A user could install or enable the skill believing it cannot trade or touch wallets, while related docs describe capabilities that could affect real funds if implemented or exposed.
These are strong safety assurances, but another supplied artifact describes an agent trade-execution flow using executeSwap and a signer, so users may reasonably be misled about whether the SDK is strictly read-only.
- **Read-only API** — fetches public market data only - **No wallet access** — does not interact with wallets or private keys - **No trading execution** — execute modules are for quote simulation only, not live trades
Clarify whether current shipped code can ever execute swaps or use wallet signers; if it is truly read-only, remove or clearly label execution docs as non-shipped future roadmap.
If execute tools are enabled for an agent, a prompt or bad workflow could move beyond data lookup into high-impact financial actions.
The integration example shows agent tool registration including an execute module, which is not clearly limited to quote simulation in this artifact and conflicts with the read-only positioning.
.getToolManifest() // Auto-registers all 44 tools
.tools
.filter(t => ['market', 'defi', 'execute'].includes(t.module))Default to registering only read-only market/data modules, require explicit user approval before any execution-capable tool is enabled, and document exact limits of the execute module.
Providing a wallet signer to an agent-controlled SDK can authorize transactions and potentially cause financial loss if boundaries are unclear.
A signer implies wallet transaction authority, but the skill metadata only declares PRISM_API_KEY and SKILL.md says there is no wallet access or live trading.
[5] dex.executeSwap(quote, signer)
→ txHash: 0x..., filled: 0.3087 ETHDo not provide wallet signers or private-key access unless you intentionally want trading; the publisher should declare any wallet/signer requirements and add strict confirmation and scoping guidance.
