alipay-pay-for-402-service

What to consider before enabling this skill: - The skill appears to implement a coherent 402/Alipay payment flow, but it instructs the agent to download and run a 3rd-party CLI via 'npx' at runtime. Downloaded packages from npm can contain arbitrary code — verify the '@alipay/agent-payment' package and the GitHub repo (check maintainers, releases, and package integrity) before allowing runtime installs. - The SKILL.md references an environment variable (AIPAY_OUTPUT_CHANNEL) and delegates authentication to an 'alipay-bot' CLI (and an 'alipay-authenticate-wallet' skill) but the skill metadata does not declare any required credentials. Confirm where and how Alipay credentials/tokens are stored and who/what has access to them before running payment flows. - The instructions force verbatim forwarding of CLI output (including one-time signed URLs and MEDIA lines). That is necessary for the workflow but also means any content returned by the CLI will be transmitted to the user unmodified. Ensure you trust the CLI and package source to avoid accidental leak or inclusion of malicious content. - If you will use this skill in a production or sensitive environment, prefer pre-installing and vetting the CLI locally (install the alipay-bot CLI manually and audit it) instead of allowing npx to fetch it on demand. Also verify the GitHub homepage and npm package authorship and check for reviews/issue history. - Ask the skill author or maintainer to clarify: (1) what credentials (if any) are required and where they must be placed, (2) whether the alipay-bot CLI will access system secrets or keychains, and (3) why AIPAY_OUTPUT_CHANNEL is referenced but not declared in metadata. Given these gaps and the runtime download behavior, treat the skill as suspicious until you validate the CLI package provenance and the credential model.