Security checks across malware telemetry and agentic risk
This paid crypto-monitoring skill needs review because it presents random simulated data as live whale-alert intelligence and has under-scoped billing and notification behavior.
Install only if you are treating this as a demo or prototype. Do not rely on its alerts, balances, exchange-flow reports, or PnL output for trading, compliance, or security decisions unless the publisher replaces the random generators with verified live data sources. If testing it, use disposable notification credentials, verify webhook destinations, avoid sensitive wallet targets, and require an explicit billing confirmation flow before any charge is attempted.
返回: {"ok": bool, "balance": float, "payment_url": str|None}
"""
try:
resp = requests.post(
f"{BILLING_API_URL}/api/v1/billing/charge",
headers=HEADERS,
json={'embeds': [embed]
}
response = requests.post(webhook_url, json=payload, timeout=10)
if response.status_code == 204:
logger.info("✅ Discord通知已发送")
else:'timestamp': datetime.now().isoformat()
}
response = requests.post(webhook_url, json=payload, timeout=10)
if response.status_code == 200:
logger.info("✅ Webhook通知已发送")
except Exception as e:'timestamp': datetime.now().isoformat()
}
response = requests.post(webhook_url, json=payload, timeout=10)
if response.status_code == 200:
logger.info("✅ Webhook通知已发送")
except Exception as e:65/65 vendors flagged this skill as clean.