Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed paid grammar-fixing skill that sends text to a remote NEXUS service, with no local file or shell access.
Install only if you are comfortable sending text to NEXUS for processing and using its payment flow. Avoid submitting secrets, private regulated data, or proprietary drafts unless your policy allows it, and configure payment credentials with clear spending limits or approval expectations.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Or manually copy the SKILL.md to your OpenClaw skills directory:
cp SKILL.md ~/.openclaw/skills/nexus-grammar-fix/SKILL.md
The README says the skill is 'automatically invoked' when a matching task is detected, but it provides no concrete trigger conditions, scope limits, or consent expectations. In a skill that sends user text to a remote paid service, ambiguous auto-invocation increases the chance of unintended data disclosure and unexpected billing.
The skill description does not clearly warn that submitted text will be transmitted to an external host for processing. Because this is a grammar-fixing skill likely to receive arbitrary user writing, omission of an external-transmission warning can lead users or agents to send sensitive drafts, credentials, or proprietary text off-platform without informed consent.
The README explicitly instructs sending user-provided input to an external network endpoint. External transmission is expected for a hosted service, but in the context of an automatically invoked skill, this becomes security-relevant because arbitrary text may be exfiltrated to a third party, potentially including confidential or regulated data.
# Step 1: Get the x402/MPP challenge
curl -X POST https://ai-service-hub-15.emergent.host/api/original-services/grammar-fix \
-H "Content-Type: application/json" \
-d '{"input": "your query here"}'
# Returns 402 + WWW-Authenticate: Payment header
The manifest description and capability description say only "Fix grammar, spelling, and improve writing," which is a very broad natural-language trigger likely to match many ordinary editing requests. The file does not provide narrower trigger phrases, activation boundaries, or negative examples to distinguish when this skill should or should not be invoked.
The skill sends arbitrary user-provided text to an external third-party service and includes a payment proof header, creating a real data exfiltration boundary outside the local agent environment. While this is the intended design of a remote SaaS skill rather than obviously malicious behavior, it is still security-relevant because sensitive prompts, proprietary text, or regulated data could be transmitted to an external operator without sufficient minimization or trust validation.
curl -X POST https://ai-service-hub-15.emergent.host/api/original-services/grammar-fix \
-H "Content-Type: application/json" \
-H "X-Payment-Proof: $NEXUS_PAYMENT_PROOF" \
-d '{
The file consistently describes a grammar-fixing service, but the tag list includes health-monitoring and budget, which are not justified by the stated purpose anywhere else in the document. This suggests capability signaling beyond the skill's documented function, even though the code/documented behavior itself does not implement those functions.