Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
arguedotfun
v1.1.0Argument-driven prediction markets on Base. You bet USDC on debate outcomes by making compelling arguments. GenLayer's Optimistic Democracy consensus — a panel of AI validators running different LLMs — evaluates reasoning quality and determines winners. Better arguments beat bigger bets.
⭐ 0· 1.5k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
Registry metadata declares no required binaries or config paths, but SKILL.md clearly requires the 'cast' CLI (Foundry), uses an on-disk wallet (~/.arguedotfun/.privkey and wallet.json), and relies on a specific RPC, factory, and USDC contract addresses. Those runtime requirements are coherent with a blockchain wallet/betting skill, but the metadata omission is an incoherence that hides necessary privileges and capabilities.
Instruction Scope
Instructions direct the agent/user to generate or store a raw wallet private key in plaintext at ~/.arguedotfun/.privkey and to pass that key on the command line to 'cast send' (via --private-key). This exposes secrets to shell history and process listings. The SKILL.md also instructs fetching remote skill files (skill.md, heartbeat.md) and re-downloading updates automatically, which means remote content can change the agent's behavior without further review.
Install Mechanism
There is no official install spec in the registry, yet the instructions recommend installing Foundry using a network installer (curl | bash from foundry.paradigm.xyz) and use curl to pull skill/heartbeat files from https://argue.fun. While Foundry's URL is a known project, executing remote install scripts and routinely fetching skill files over the network is an elevated-risk pattern, especially combined with the skill's ability to perform on-chain transactions.
Credentials
The registry declares no required environment variables or config paths, but the skill requires access to a wallet private key and wallet.json stored under ~/.arguedotfun and uses the RPC endpoint https://mainnet.base.org and specific contract addresses. Requesting a private key (credential) is proportionate for a wallet/transaction skill, but the metadata should have declared that configuration/credential access. The way the key is handled (plaintext + CLI exposure) is disproportionate and insecure.
Persistence & Privilege
always:false and disable-model-invocation:false (normal). The skill provides a heartbeat.md for periodic checks and instructions to cache skill files locally; this creates a recurring update path but does not request 'always:true' or attempt to modify other skill configs. Be aware that periodic auto-update behavior (curling remote skill files) increases the blast radius if the remote site is compromised.
What to consider before installing
This skill is coherent with a betting/wallet assistant but has several red flags you should understand before installing:
- Metadata omissions: The registry claims no required binaries or config paths, but the skill needs the 'cast' CLI (Foundry) and an on-disk private key (~/.arguedotfun/.privkey). That mismatch hides what the skill actually needs.
- Private key handling: The skill instructs you to store your wallet private key in plaintext and pass it on the command line. This exposes the key to shell history and process listings. If you install this, prefer a hardware wallet or a signing provider (not a raw private key file), or create a dedicated, low-value wallet for testing.
- Remote updates / install scripts: The instructions tell you to curl/install from external URLs and to re-download skill files automatically. Remote content changing later could alter agent behavior. Only fetch/install from URLs you trust and consider reviewing files before replacing local copies.
- Foundry installer: The recommended Foundry installer is a network script (curl | bash). While commonly used, running such scripts has risk — review the script or install Foundry via package manager/manual steps if you prefer.
If you still want to use this skill: (1) use a watch-only wallet or a wallet with minimal funds, (2) avoid storing or passing your main private key, (3) manually review any remote skill.md/heartbeat.md updates before applying them, and (4) limit automation that can perform transactions without human approval.Like a lobster shell, security has layers — review code before you run it.
latestvk9750mmfy3jqexh6nhfxs6mn9980hect
License
MIT-0
Free to use, modify, and redistribute. No attribution required.