Rng Provably Fair
v1.0.0Provably fair random number generation with on-chain seed anchoring — Keno, Roulette, Dice for agent entertainment
⭐ 0· 90·0 current·0 all-time
byOrion@drivenbymyai-max
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (provably‑fair RNG for games) matches the SKILL.md instructions which provide curl examples to a public RNG/verify API. The functionality described (server seed hash, verify, on‑chain anchoring) aligns with the endpoints shown. Minor metadata inconsistency: registry listing reported no homepage, but SKILL.md metadata and instructions reference https://sputnikx.xyz/rng.
Instruction Scope
Instructions are narrow and only demonstrate GET requests to the external API and a verification endpoint; they do not ask the agent to read local files, environment variables, or other system state. However, the skill sends requests to a third‑party host (sputnikx.xyz), so any data you include (for example a client seed) will go to that server — avoid including secrets or private data in requests.
Install Mechanism
No install spec and no code files — lowest risk from installation. Nothing is written to disk or fetched during install because the skill is instruction-only.
Credentials
The skill declares no required environment variables, credentials, or config paths — this is proportionate to an integration that simply calls public HTTP endpoints.
Persistence & Privilege
always:false and user-invocable:true; the skill does not request persistent privileges or modify agent/system configuration. Autonomous invocation (model invocation enabled) is the platform default but is not coupled with other concerning privileges here.
Assessment
This skill is an instructions-only wrapper around a public RNG service. Before installing: verify you trust https://sputnikx.xyz (review any public audits or on‑chain anchors they claim), do not send passwords, API keys, or other sensitive data as the 'client seed', and confirm the on‑chain proofs yourself if you rely on fairness claims. If you need higher assurance, prefer a self‑hosted or auditable implementation (or check for independent audits of the service). Also consider legal/regulatory and age restrictions for casino/gambling features in your jurisdiction.Like a lobster shell, security has layers — review code before you run it.
latestvk97fcyetfmcym4mcwe4c0bwadd83c90j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
