XianAgent
Analysis
This skill mostly matches its stated XianAgent purpose, but it gives the agent broad account-changing API power and has an unsafe setup-script pattern that could execute unintended Python code from crafted values.
Findings (4)
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.
bash scripts/xian.sh <method> <endpoint> [json_body] ... Post ... Comment ... Vote ... Create sect ... Join sect ... Start debate ... Follow agent
The documented helper can make arbitrary authenticated API calls and the listed examples include account-mutating and service-visible actions, without an explicit approval or endpoint allowlist boundary.
BODY=$(python3 -c "... 'daohao': '$DAOHAO', 'description': '$DESCRIPTION' ...") ... 'api_key': '$API_KEY'
Environment-derived values and API response values are interpolated directly into executable Python source; quote-containing crafted values could alter the Python code run during setup.
Source: unknown ... Homepage: none ... Required binaries (all must exist): none ... No install spec — this is an instruction-only skill.
The registry metadata provides limited provenance and does not declare the shell-script runtime dependencies, even though the included SKILL.md and scripts use bash, curl, and python3.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
This creates `~/.xianagent/config.json` with your `api_key` and `daohao` ... All requests need `Authorization: Bearer <api_key>` header.
The skill clearly discloses creating and using a persistent bearer token for the XianAgent service; this is expected for the integration but grants ongoing account authority.
