X402 Cfo
ReviewAudited by ClawScan on May 10, 2026.
Overview
This skill is purpose-aligned for payment budgeting, but it asks an agent to install and use an unpinned payment package with wallet-spending authority and persistent audit logs.
Review and pin the x402-cfo npm package before use, connect only a limited wallet, configure conservative budget limits, and protect the generated ledger file because it contains financial activity details.
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 package fetched at install time could change over time or differ from what was reviewed, and it would be used in a financially sensitive workflow.
The skill instructs runtime installation of an unpinned npm package, while the provided artifacts include no package code or install spec. That package is then expected to handle wallet-backed x402 payments.
npm list x402-cfo 2>/dev/null || npm install x402-cfo
Only use this with a pinned, reviewed package version from a trusted source, and verify the npm package before connecting any wallet.
If configured with a real wallet, the agent may spend funds on paid APIs up to the configured limits without asking for each payment.
The skill delegates wallet-based payment authority to the CFO package and allows automatic payment decisions under configured budgets.
wallet: walletInstance, // Your x402-compatible wallet ... The CFO will automatically: ... Pay the x402 challenge if approved
Use a dedicated low-balance wallet, set strict budgets and blocklists, and require explicit user confirmation for paid requests where possible.
The ledger may reveal what paid services were used, spending amounts, timestamps, and policy decisions.
The skill stores a persistent local audit ledger containing detailed financial activity and endpoint history.
storage: new JsonFileStorage('./x402-cfo-ledger.json') ... Full ledger: every payment decision with timestamp, amount, URL, status, reasonStore the ledger in a protected location, avoid committing it to source control, and delete or rotate it when no longer needed.