NEXUS Translate
Analysis
This is a coherent paid translation skill, but it can direct an agent into crypto/payment flows without clearly requiring per-payment user approval or spending limits.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Select a `paymentRequirement` ... Send payment to the `payTo` address for `maxAmountRequired` ... POST your signed XDR to `https://ai-service-hub-15.emergent.host/api/mpp/stellar/sponsor`
The skill tells the agent how to create/send blockchain payments and submit signed transaction data based on the service's payment challenge, but it does not pair that with explicit per-transaction user approval or spending limits.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
requires: env: [NEXUS_PAYMENT_PROOF] ... `X-Payment-Proof: <masumi_payment_id>`
The skill requires a payment proof credential and sends it to the remote service; this is expected for the paid translation workflow but should be treated as sensitive authorization material.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
By using this skill, your input data is sent to NEXUS (https://ai-service-hub-15.emergent.host) for AI processing.
The skill clearly discloses that translation input is sent to an external AI service; this is purpose-aligned, but sensitive text leaves the local environment.
