Skillv2.3.4

ClawScan security

MasterCard AgentPay | Compatible compatible cards, wallets & payments · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignMar 12, 2026, 6:14 PM

Verdict: Benign
Confidence: high
Model: gpt-5-mini
Summary: The skill's requests and runtime instructions are consistent with a payment/checkout integration and only require the single CreditClaw API key it declares.
Guidance: This skill appears coherent for enabling agent payments. Before installing: (1) Only provide a CreditClaw API key you control and understand grants spending capability; treat it as a secret. (2) Ensure the agent runtime can keep decrypted card data strictly ephemeral (in-memory) and that logs/telemetry will not capture card fields or the API key. (3) Confirm your owner-approved spending limits, approval_mode, and blocked categories in spending.md to avoid unexpected charges. (4) If you do not want autonomous spending, disable or tightly scope agent autonomy (or keep approval_mode set to ask_for_everything). If you want more assurance, verify the service at https://creditclaw.com and confirm its ownership and privacy policies before handing over real payment credentials.

Review Dimensions

Purpose & Capability: okName/description describe a payments platform and the skill only requests CREDITCLAW_API_KEY and documents API calls to https://creditclaw.com/api/v1 — these requirements match the stated purpose (creating checkouts, wallet signing, encrypted-card flow, management).
Instruction Scope: okSKILL.md and companion docs instruct the agent to call CreditClaw API endpoints, poll status, request single-use decryption keys, and perform ephemeral decryption in memory. They do not instruct reading unrelated files or exfiltrating secrets to other domains; the docs explicitly warn not to send the API key to any domain except creditclaw.com/api/*.
Install Mechanism: okThis is an instruction-only skill with no install spec and no code files to execute. No packages, downloads, or extract steps are required — minimal surface area for code-install risk.
Credentials: okOnly a single environment variable (CREDITCLAW_API_KEY) is declared and used. That is appropriate and proportional for a service that performs authenticated payment operations. No unrelated credentials or config paths are requested.
Persistence & Privilege: okThe skill is not marked always:true and does not request system-wide configuration or credentials belonging to other skills. It does instruct ephemeral handling of decrypted card data (must be kept only in memory), which is appropriate for its function.