Real Skill packageSource verifiedClawHub registry

xrp-fleet-data

Buy live XRP Ledger telemetry and proxied ledger/account reads over HTTP with per-request XRP payments (x402 v2) — no account, no API key, no infrastructure. Use when an agent needs fee pressure / transaction queue depth / ledger liveness / a `ledger` or `account_info` read and can pay drops (100–200 per call) or a flat 30-day plan.

Identity and source

Publisher attributionfudge144registry owner unverified by skillvetai
Functional categoryDevOps, Cloud & Observabilityautomatically inferred · 64% rule confidence
Package forminstruction with code3 recorded files
Canonical sourceClawHub registryclawhub:fudge144:xrp-fleet-data
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 10/2/2026.claude/skills/xrp-fleet-data

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 10/2/2026.agents/skills/xrp-fleet-data

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 10/2/2026skills/xrp-fleet-data

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @fudge144/xrp-fleet-data
clawhub inspect @fudge144/xrp-fleet-data --version 1.0.2

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
3 / 3 inspected as text
Checked
10/2/2026, 5:33:28 AM
Scanner
0.1.3
Policy
1.0.3
4 inferred permission indicators
  • network access — automatically inferred
  • filesystem read — automatically inferred
  • filesystem write — automatically inferred
  • credential access — automatically inferred
3 dependency and API indicators
  • api: clawhub.ai
  • api: d5e7fd5a.xrplclaw.com
  • api: evil.example
External clawhub result: suspicious

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
10/1/2026, 11:42:53 PM
Release binding
Matches this record
  • skillspector: suspicious
  • llm: suspicious

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:b6cd4117889bb02aaaea46221bb91834cc02d800ad872b8a00fc6fc713dec0f6
Show up to 3 recorded paths
  • scripts/guarded-buy.cjs
  • skill-card.md
  • SKILL.md

Source changelog

1.0.2 security remediation of the auto-pay finding, done properly: the client no longer wraps an auto-paying fetch. It gates the received challenge, presigns a Payment built ONLY from that gated object, audits the exact pre-sign bytes (Payment type, signer Account, Destination==payTo, Amount==gated drops, SourceTag, invoice Memo present, LastLedgerSequence set) before calling sign(), pins a bounded horizon (MAX_TIMEOUT_SECONDS=300) and expected sourceTag, verifies the seller receipt tx hash equals its own signature hash, and reserves spend in a persisted daily ledger. Adds offline structural proof (--selftest, 16 gates) plus a harness proving refusals never write spend; docs updated to warn against cap-on-probe/pay-different-invoice patterns.