ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Free Ride Xiaoshu

v1.0.0

Manages free AI models from OpenRouter for OpenClaw. Automatically ranks models by quality, configures fallbacks for rate-limit handling, and updates opencla...

⭐ 0· 47·1 current·1 all-time
by@xiaomaju-888
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
ℹ
Purpose & Capability
The name/description match what the code and SKILL.md do: fetch free models from OpenRouter, rank them, and update OpenClaw config. Modifying ~/.openclaw/openclaw.json and restarting the gateway is expected for this purpose. However, registry metadata at the top claims 'Required env vars: none' while skill.json and SKILL.md require OPENROUTER_API_KEY — an inconsistency in declared requirements and metadata source information (source/homepage unknown) that should be resolved.
ℹ
Instruction Scope
SKILL.md instructs only the actions necessary for the stated purpose: set OPENROUTER_API_KEY, install the freeride package locally, run freeride commands, and restart openclaw gateway. It explicitly reads/writes only ~/.openclaw/openclaw.json and stores caches/state under ~/.openclaw — which is within the skill's domain. No instructions request unrelated system files or unrelated credentials. Note: the SKILL.md recommends installing (pip install -e .) which results in code being written/executed locally — this expands runtime surface compared to a purely instruction-only skill.
ℹ
Install Mechanism
There is no registry install spec in the metadata shown, but the package includes setup.py, requirements.txt, and SKILL.md/README install instructions that direct the user to pip install -e . (and an npx clawhub install command in README/skill.json). The Python dependency is only 'requests', from PyPI (reasonable). This is not high-risk, but the mismatch between 'no install spec' in registry metadata and multiple install instructions in files is a packaging/integrity inconsistency to be aware of.
ℹ
Credentials
The skill requires a single service credential (OPENROUTER_API_KEY) which is proportional to the described functionality. The code will also read the key from ~/.openclaw/openclaw.json if present. That behavior is reasonable, but the top-level registry metadata incorrectly lists no required env vars while skill.json and SKILL.md declare the API key as required — this discrepancy reduces confidence in the metadata accuracy.
✓
Persistence & Privilege
always: false and normal autonomous invocation are used. The skill writes only to its own cache/state files and to the OpenClaw config (~/.openclaw/openclaw.json) which is expected for a skill that reconfigures OpenClaw. It does not request system-wide privileges or modify other skills' config beyond the stated keys.
What to consider before installing
This skill appears to do what it says (manage OpenRouter free models and update your OpenClaw config), but there are a few red flags to check before installing: - Verify the source/trust: the registry metadata lists no homepage/source; confirm the package origin (GitHub repo) and that the author is trustworthy. Clone and inspect the repository before pip installing. - Back up your OpenClaw config (~/.openclaw/openclaw.json) before running the tool; it will modify agents.defaults.model, fallbacks, and models. - Confirm the OPENROUTER_API_KEY requirement: provide a dedicated OpenRouter key and consider its permissions; the watcher will make frequent API calls (health checks and rotations) which will use that key. - Because the package installs code (setup.py) and creates CLI binaries, review main.py and watcher.py fully (they are present and straightforward) to ensure there are no hidden network endpoints or unexpected host URLs. The code appears to call only openrouter.ai and uses local cache/state files under ~/.openclaw. - If you want lower risk, run the watcher in a constrained environment (not with elevated privileges), and test 'freeride list' and 'freeride status' first to observe behavior. Given the metadata inconsistencies (declared required env var absent from top-level registry metadata and missing/duplicated install instructions), proceed with caution and manual review before granting persistent use.

Like a lobster shell, security has layers — review code before you run it.

latestvk978sjmk4c70sb65px81f3n1ks849znm

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments